#Scott McHugh
1 messages ยท Page 1 of 1 (latest)
A screenshot of the network calls I see
You mentioned this started happening recently. Has anything network-wise changed in this timeframe? Also, is this connectivity issue intermittent? Have you seen any successes recently?
I reached out to the customers IT support, they indicated no network changes have occurred. I'd also asked about firewalls etc, but they indicated it was fully open. The issue is persistent, no successes since the problem started occuring
(their network IT person* - I work for the software company that provides their point of sale)
if I try to hit that url in my browser (in my computer, on the. same network) I am unable to. I found an article suggesting not all DNS servers will do the local redirect needed, so I switched my laptop (macbook pro) system settings to use the google one I saw referenced (https://documentation.commerce7.com/troubleshooting-stripe-terminal-connectivity), but no luck
in my terminal I tried a nslookup of "nslookup 192-168-33-128.device.stripe-terminal-local-reader.net" (similar url, but minus the random string before device and the https qualifiers), and that resolved correctly
Ok gotcha. Thanks for all the details. Let me reach out to a colleague so I can get a second pair of eyes on this
thank you- really appreciated!
Hello ๐
I am a bit confused by the error message in the console as it says unable to connect to Verifone terminal but WisePOS E isn't really a verifone terminal.
yeah, that seemed odd to me as well
I know the same setup does work when I test from my home network (that call resolves)
Based on the warning above the error, it looks like DNS resolution is failing. We have general guidance on how you can handle DNS resolution failures
https://stripe.com/docs/terminal/readers/bbpos-wisepos-e#reader-has-ip-address-and-can-communicate-wi[โฆ]-but-not-with-your-point-of-sale-application
Another thing you can try is to connect to a portable hotspot
good call, I'll try that
Yeah, that would help us confirm if the issue is with their network
ok, yeah when I hit the device off my hot spot it does make that request alright- and I can get to the point where it finds the reader, then when I go to process a sale it shows the 'waiting for payment' on the reader as expected. The jackrabbit requests come back with a status of
status 200 ok, no payload, which seems clean
Right, so looks like something in their network configuration is preventing Reader DNS from resolving..
thank you for your help! Been testing variations of the set up. I appreciate your time.
NP! ๐ Happy to help