#bomsn

1 messages · Page 1 of 1 (latest)

pulsar zenithBOT
lunar viper
#

Thanks for the update. Watching your video

gloomy parcel
#

Thanks for looking

lunar viper
#

Yep yep, sorry was a bit busy in other threads. Catching up properly now

#

Still thinking on this. It is definitely good that your terminal appears to have DNS working. Trying to think of what might be causing these issues given that

gloomy parcel
#

Sure no problem, take your time, I'll step out now, but will check back later

charred hinge
#

Hello @gloomy parcel, I'm taking over. Are you still getting the same Could not communicate with the Reader. error as before? If so, can you tell me what operating system and web browser you're using with Terminal?

gloomy parcel
#

Yes, we are still getting the issue, we are using windows 10 and Google Chrome. Note that it worked before but it doesn't seem consistent. We have also used it on a different physical location and it worked without changing DNS, but unable to re-test again as this was one time test and no longer at the same location.

Also note that it worked on the current router after we changed browser DNS yesterday to Google Public DNS, but this trick will not work today

charred hinge
#

In the error message there's a URL, like https://192-168-1-234.iq7zwvwgo6wnykhkkotg.device.stripe-terminal-local-reader.net (that one is from your earlier thread). Can you take that URL, strip off the https:// part, and then open Command Prompt and run nslookup <hostname> and see what results you get? For example, it would be nslookup 192-168-1-234.iq7zwvwgo6wnykhkkotg.device.stripe-terminal-local-reader.net for your earlier error.

#

Also, please make sure to do this on the same device you're trying to use the Terminal reader with.

gloomy parcel
#

Ok, can I do this tomorrow please? would you stay on the thread?

charred hinge
#

You can do it tomorrow, but you'll need to start a new thread by asking in #dev-help. This server is for realtime help and we don't keep inactive threads open for very long.

gloomy parcel
#

Or, I'll start a new thread and try to refer to this one. What results should I expect when I use nslookup and how can I troubleshoot in case you're not around?

charred hinge
#

You should see the hostname resolve to an IP address. Something like this (although it will be a bit different on Windows I think):

❯ nslookup 192-168-1-234.iq7zwvwgo6wnykhkkotg.device.stripe-terminal-local-reader.net
Server:        10.0.1.1
Address:    10.0.1.1#53

Non-authoritative answer:
Name:    192-168-1-234.iq7zwvwgo6wnykhkkotg.device.stripe-terminal-local-reader.net
Address: 192.168.1.234
#

If you get a message saying it can't find the result instead, that's the issue (the hostname cannot be resolved to an IP address), and you'll need to figure out why that is. Usually it's because the DNS server being used won't resolve hostnames to local IPs, which means you have to change a router configuration or use different DNS servers.

#

If you do get the IP address back as expected the next step would be to try and ping the IP address, like this: ping 192.168.1.234

#

If the pings don't work then there's a connectivity issue of some kind, and you'll need to figure out the network issue that's stopping the pings from getting through.

#

Beyond that it can go in a lot of different directions.

gloomy parcel
#

Ok thanks, I'll get back with the results. Thanks again