#waveydavey00 - terminal connectivity
1 messages · Page 1 of 1 (latest)
👋 Have you spoken to Gymdesk support about this? We don't know the specifics of their integration, so we don't know what are the prerequisites needed to get this running end to end
I have they say they don't know that I should contact Stripe
I have it integrated via their platform
Did they provide you with any logs/guidance on what specifically you need to ask about?
I don't know what "searching for card reader" means in terms of what state/error their integration would be in, so we'd need more details on what their integration is doing at that point
When we go to process a payment it just stays searching for card reader so I wasn't sure if I needed some other app or something ??
The reader is turned on and connected to wifi
Both devices are connected to the same network
I don't know for certain whether you need a separate app (again because we don't know what Gymdesk's integration is doing), but I assume you wouldn't need to download anything else
That would be my guess as well
I can see if I can find anything else if you share the reader serial number, but no guarantees - you still may need to go to gymdesk and push for more details on what's wrong
thanks! let me see what i can find
So it looks like there's an issue with connecting to the reader - usually these errors are caused by DNS issues or a firewall. Can you check the settings on your reader and see whether DNS resolution is successful (https://stripe.com/docs/terminal/readers/bbpos-wisepos-e#reader-has-ip-address-and-can-communicate-with-stripe,-but-not-with-your-point-of-sale-application)
Yeah this is why I recommended going through Gymshark to get help - since you're using an integration they built it should be on them to help you get everything working
The device says terminal events connectivity "Pending"
Maybe there's some setting in Stripe?
one sec - just grabbing my reader to check something
What does it say for "DNS resolution" specifically - not the terminal events connectivity
I'll check
But it's connecting from my desktop but not my iPad which are on the same network
Passed on DNS reslolution
Maybe it can't connect to two devices at once even though they are on the same network?
Surely it doesn't make a difference if it's on a Macbook or an iPad?
It shouldn't make a difference, but it's possible your ipad has different DNS settings then your macbook does
ok
I also want to clarify - you can only connect one device to a reader at a time. If your reader is already connect to one device, connecting to another will sever the connection it had before
ok so then maybe that's the issue. Let me try and connect it directly to the ipad by establishing the connection through it rather than the desktop
so i reconnected it via the ipad and it is still searching
for the reader. I ever re started the reader
Then it's likely a difference in the DNS settings for the ipad and you'll have to modify them
ok what do I need to do?
I added those DNS setting to the iPad. Still no luck
One other thing I'd try is starting up a hotspot and having both the ipad and reader join that network and see if that helps
I need to head out, but @random mason can answer any other questions
Yes the most important thing is ensuring the devices can communicate with one another, which sounds like is still prevented.
Your POS needs to be able to connect directly to your Terminal reader.
https://stripe.com/docs/terminal/readers/bbpos-wisepos-e#reader-has-ip-address-and-can-communicate-with-stripe,-but-not-with-your-point-of-sale-application
https://stripe.com/docs/terminal/readers/verifone-p400#reader-has-ip-address-and-can-communicate-with-stripe,-but-not-with-your-point-of-sale-application
Readers use a hostname such as
10-0-0-5.abc123.device.stripe-terminal-local-reader.net where 10-0-0-5 represents the hyphen-delimited local IP address of the reader and abc123 can be any random string. The exact string typically is not relevant, but you can get it from the base_url on each result from discoverReaders().
From the POS device, the following commands are informative diagnostics:
1/ nslookup 10-0-0-5.abc123.device.stripe-terminal-local-reader.net
This needs to resolve to the local IP address (eg 10.0.0.5). If it does not, it is likely that your router or other DNS provider is using DNS Rebinding protection.
2/ ping 10-0-0-5.abc123.device.stripe-terminal-local-reader.net
This needs to be able to connect to the reader. If it cannot, it is likely that the network is preventing device-to-device direct connections as a security measure.
The results of 1 & 2 above will help narrow the scope of the network connectivity issues between the POS and reader
Depending on the exact issue, correction might involve your network administrator making changes.
So i Wouldn't think it's at a router level because my MacBook can connect but the iPad cannot and we are on the same network
Possible, but hard to say without running the diagnostics
But yes its a good sign that another device can connect
It does suggest the issue might lie with the ipad config, or the network treatment of the ipad
waveydavey00 - terminal connectivity
how would i run diagnostics?
You may need a network diagnostic utility app, i don't think this is supported natively on ipads
Ok so turns out it works on Safari on the ipad but NOT in Chrome. But it DOES work in Chrome on the Macbook duu
Ah, that's very interesting, and might be related to browser certificates