#jainnikesh - Terminal Connectivity
1 messages · Page 1 of 1 (latest)
Hello!
We are getting this error can someone help
POST https://192-168-1-182.mrg3qsqdy3tcbm474od5.device.stripe-terminal-local-reader.net:4443/protojsonservice/JackRabbitService net::ERR_CONNECTION_TIMED_OUT
Hello
That error usually indicates either your POS device cannot resolve the IP of the Terminal reader, or the Terminal reader is not on the same network as your POS device. What device are you using with the Terminal reader?
hi
actually it's working properly previously
and sudden this error come
even we have not changed anything
I'd be happy to help you fix the error if you can tell me what device you're using with the Terminal reader?
Right, that's the Terminal reader. What device are you trying to use with it? A Windows computer? A Mac? An iPad? Something else?
Okay, let's do two things. First, check the network diagnostics on the Terminal readers. Do you have one of them in front of you right now?
Okay, let me know when you have it.
actually this is our client
not sure why it's showing offline
in stripe dashboard
why riverbend and shashta both showing offline
their office internet was down since 12
but is not working before that
so troubleshooting is not work here
do we have any other options ?
So you don't have access to the Terminal readers having the issue?
yes
There's not much I can do to help if you don't have access to the readers. The first step is to check and see if they're able to connect to the Internet and to Stripe by checking their diagnostics screen, and that needs to be done on the Terminal reader itself.
okay
So there is no issue in stripe side right
This is because either terminal or either network?
I doubt it's a Stripe issue, but I can't say for sure without having you run some diagnostics and tests.
Because when it's working previously and then sudden stop
So I am asking
And we have not changed any network on stripe terminal or system
And jackob service
We are getting this service offline many Times
And then suddenly it's start working without any changes
It sounds like a network/Internet connectivity issue to me, but again, hard to say without being able to run tests.
Wow now all terminal back online