#hendie_error
merry kilnBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1267966504947941449
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
serene cobaltBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- hendie_eftops-not-accepted, 4 days ago, 30 messages
- hendie_hendie-eftpos-error, 4 days ago, 6 messages
- hendie_api, 4 days ago, 5 messages
- hendie_unexpected, 6 days ago, 6 messages
neon sable
when used from stripe.js shows the jackrabbit service failing continuously.
Can you share more context here? What does the end customer see in this case?
tough ferry
the terminal is not showing anything
any idea why the terminal is not updating to the latest version?
neon sable
Give me a few more minutes please. I noticed our docs still state that version 2.24.2.0 is the latest: https://docs.stripe.com/terminal/readers/bbpos-wisepos-e
tough ferry
ok
safe blade
Hello, looking in to the firmware upgrade aspect. Was this terminal working previously? Also I see these terminals are at the same location, but just to confirm are they on the same network? Also would it be possible to try to connect to the terminal that is failing more from the point of sale device that is successfully able to connect to the terminal with the newer firmware?
And have you been able to manually reboot the reader on the older firmware recently? It looks like the newer firmware was released widely somewhat recently. So there is a chance that it hasn't been able to automatically check for the update yet but a reboot could help force it to check
tough ferry
The terminals are actually with two different engineers, so yes the networks are different
I can ask the guy with the older firmware to reboot ...
how does one "manually"reboot these terminals?
neon sable
You can follow the steps here: https://docs.stripe.com/terminal/payments/setup-reader/bbpos-wisepos-e#power
tough ferry
we got it rebooted, and to the latest firmware, but it's still not working
this is what the console log shows
you can see all the calls to the jackrabbit service failing
have you any suggestions to troubleshoot possible local network filtering that may be happening.
neon sable
Is it possible to try connecting this reader to a different network?
Do you know if the network that it's currently connected to uses WPA-E or WPA2-E configurations?
tough ferry
We can register the terminal, and I guess that works because your backend talks to ther terminal from the Internet, but the jackrabbit service is trying to talk to the terminal on the local network
not sure, I can ask the engineer ... hang on
both your laptop and the terminal is on the 192.168.0.x network?
oops, sorry that was for my eng
wider view of the network tab
he says they are both on the same subnet
status column widened
neon sable
Is your eng able to use a different network temporarily to rule out any network-specific issues?
neon sable
I see, that helps!
tough ferry
on a previous occasion a Stripe tech suggested hardcoding the router DNS to offer a static local ip to the terminal. Wondering is that is strictly necessary.
neon sable
That at least points to something on the original network