#bwurtz999

1 messages · Page 1 of 1 (latest)

candid jacinthBOT
tepid cloak
#

Let me get a colleague who's better with terminal to assist

worn niche
#

Thank you

brittle ingot
#

can you run a network diagnostic from the settings menu in the reader and see what that says?
https://stripe.com/docs/terminal/readers/bbpos-wisepos-e#updating

we do have some telemetry from the reader but it's mostly saying it can't connect to our servers due to various network errors and SSL timeouts so maybe something on your network is blocking/firewalling something

worn niche
#

It's back up and running now, but there was a 30 minute period or so where the screen wouldn't update

#

And I ran a network health check during that time period

#

and it said 'Your current network is healthy'

#

This completely shut down our service because we couldn't take card payments

#

Why is it now suddenly working?

#

It's using the same network as before

brittle ingot
#

maybe it was installing an update?

worn niche
#

There was nothing on the screen to indicate that. It was the standard screen

#

Would it do that in the background and interrupt service?

brittle ingot
worn niche
#

No, it was working at the same location yesterday

#

Something strange was going on. I could see the Ethernet symbol on the reader screen, and at the same time the Dashboard was telling me it was offline

#

After a restart it started working again

#

Do you know what would cause this behavior?

brittle ingot
#

not really no

brittle ingot
worn niche
#

Interesting

#

Ok

#

And you don't see any strange behavior from this reader right now do you?

brittle ingot
#

no

#

looking at telemetry all I really see is that at 0:54 (UTC) it rebooted(as I mentioned above, it does that) and then we have no more telemetry until 13:10 UTC a couple of hours ago

#

there ares some mentions of scanning for Wifi so note https://stripe.com/docs/terminal/payments/setup-reader/bbpos-wisepos-e#network-priority like

The BBPOS WisePOS E resets its priority to Ethernet when rebooting. Even if previously configured for WiFi, the reader switches to Ethernet if it detects an Ethernet cable connection while starting up.
maybe in your setup you previously were using Wifi and it switched to Ethernet and your network settings are different there

worn niche
#

Yeah the reboot must've fixed whatever was going on