#bababiff
1 messages · Page 1 of 1 (latest)
Hello 👋
Can you share the reader serial numbers?
Also are you using Server Driven SDK or something else?
One of the serials: WSC513124021629
Javascript API
Have you tried connecting to a mobile hotspot?
No
I can try stand by
Well thats not good, just completed a transaction, we have not changed anyhting on our network any clue what could be the issue
hotspot worked immediately
We have Comcast cable internet
Not sure, It working on hotspot makes me think comcast changed something on their end.
Also, we haven't heard of any other reports of readers not working this morning.
all other systems on the network are functioning normally , it must have something to do with the weird dns entry that the api uses to communicate to the local device
do you mean you have custom DNS servers configured locally?
on both the terminal and pos
Maybe try changing them to google or cloudflare DNS?
Ah hmm interesting
whats further strange is that i did not do anything special with the hotspot just connected the two devices and completed a transaction
so whatever dns from google fi (most likely google) worked on automatic
yeah try moving all the DNS addresses to Google and see if that behaves differently
Hello Pompey, do you have any insight? I am trying to reach out to comcast but have little faith they will be able to help
Hello, still catching up and will get back to you. It is great that the hotspot works at least that can help us narrow down what this may be a bit