MopeyGecko | Stripe Developers | Page 1

solar lagoonBOT Sep 23, 2022, 8:14 AM

#

verbal ocean Sep 23, 2022, 8:14 AM

#

Hi there!

#

Pasting your other messages in this thread:

Does anybody have any ideas where I should start troubleshooting?
It happened once last week too but seemed to resolve itself

#

Which Terminal device are you using? Can you share its ID?

calm owl Sep 23, 2022, 8:16 AM

#

Reader ID - tmr_EsjwuguIp8onLz

strange basalt Sep 23, 2022, 8:22 AM

#

most likely this is a DNS issue, can you try some of the steps at https://support.stripe.com/questions/the-stripe-terminal-sdk-is-encountering-dns-errors-when-connecting-to-an-internet-reader ? In particular, can you try running nslookup 192-168-0-35.jtzl2ez77g3vwg3anxx6.device.stripe-terminal-local-reader.net on your PC that connects to the reader?

calm owl Sep 23, 2022, 8:26 AM

#

Thanks that gives me somewhere to start. nslookup seems to be successful but I'll experiment with router DNS settings

#

andy@Andys-2021-MBP ~ % nslookup 192-168-0-35.jtzl2ez77g3vwg3anxx6.device.stripe-terminal-local-reader.net
Server: 192.168.0.1
Address: 192.168.0.1#53

Non-authoritative answer:
Name: 192-168-0-35.jtzl2ez77g3vwg3anxx6.device.stripe-terminal-local-reader.net
Address: 192.168.0.35

strange basalt Sep 23, 2022, 8:30 AM

#

cool. and what happens if you ping 192.168.0.35 ?

calm owl Sep 23, 2022, 8:34 AM

#

request timed out. OK internal network issue. Thanks for your help.

strange basalt Sep 23, 2022, 8:39 AM

#

yep or the reader is not turned on or something, hard to say. But also yes, maybe you have an internal firewall blocking the connection across the LAN. It's worth at least checking the reader and making sure it's turned on and it actually has that IP assigned, from the diagnostic screen

calm owl Sep 23, 2022, 8:45 AM

#

yeah IP seems to be assigned correctly from diagnostics. Sorry to bother you.

#MopeyGecko