#artdudejoe
1 messages · Page 1 of 1 (latest)
Hey there
Karbi isn't available right now but I'd be happy to help
Can you summarize the state here?
I am using terminal API to hand off paymentIntent to a BBPOS WISEPOS_E reader using $stripe->terminal->readers->processPaymentIntent(
Response "Reader is currently unreachable, please ensure the reader is powered on and connected to the internet before retrying your request."
Ah okay
So yeah it sounds like the Reader hasn't actually been connected to your application yet
Are you using the Server-driven approach or one of the SDKs?
Server driven, yes.
Got it, and are you testing with a simulated reader or an actual reader?
I created a location and reader.
Actual reader
There's a theory that it wasn't setup correctly.
The reader ID: tmr_E0P5xwBFWrL8en
Hmm yeah you actually should only need to register your reader with Server-driven. Shouldn't need to use a connection token
That was my thought.
Let me try that. I need to do a whole VPN thing and get off here first. BRB
👍
Here's the one reader object
Stripe\Terminal\Reader Object
(
[id] => tmr_E0P5xwBFWrL8en
[object] => terminal.reader
[action] =>
[device_sw_version] =>
[device_type] => bbpos_wisepos_e
[ip_address] => 192.168.86.64
[label] => Accname Main Street
[livemode] =>
[location] => tml_E0P5xwwLGxI3Mb
[metadata] => Stripe\StripeObject Object
(
[oa_accid] => 1
[oa_accname] => accname
[oa_locationid] => 4
)
[serial_number] => WSC513223000030
[status] => offline
)
Cool so it is registered fine but looks to not be connected to the internet so that's the issue
I've got to run but @undone quarry can help further
"Offline"?
Cool. Thanks @marsh plume
Hi @undone quarry Can you help me get the reader connected properly?
What seems to be the issue here?
I am using terminal API to hand off paymentIntent to a BBPOS WISEPOS_E reader using $stripe->terminal->readers->processPaymentIntent(
Response "Reader is currently unreachable, please ensure the reader is powered on and connected to the internet before retrying your request."
I ran $stripe->terminal->readers->retrieve( $stripe_readerid, [] ); and got
Stripe\Terminal\Reader Object
(
[id] => tmr_E0P5xwBFWrL8en
[object] => terminal.reader
[action] =>
[device_sw_version] =>
[device_type] => bbpos_wisepos_e
[ip_address] => 192.168.86.64
[label] => Accname Main Street
[livemode] =>
[location] => tml_E0P5xwwLGxI3Mb
[metadata] => Stripe\StripeObject Object
(
[oa_accid] => 1
[oa_accname] => accname
[oa_locationid] => 4
)
[serial_number] => WSC513223000030
[status] => offline
)
@marsh plume said that the reader isn't connected to the internet.
K
Alright here we go: https://stripe.com/docs/terminal/readers/bbpos-wisepos-e#troubleshooting
Done all that.
Am I looking at [status] => offline?
The device IP address is an internal DHCPd from the Google Fibre router.
But the reader cannot connect to the internet?
It says it is in "Settings"
@marsh plume said that the reader isn't connected to the internet after seeing the result array above.
Right, because the reader's status is offline
That tells me it's connected to your wifi network. What is the DNS address?
WiFi DNS servers: 192.168.86.1
Local router address
Terminal events connectivity: Pending…
Yeah the DNS server needs to be global. That address suggests the reader isn't connecting to the internet
Gotcha
How do I correct that?
If I restart the reader (in this case open settings then close them) the dashboard says it is connected. But not when I issue $stripe->terminal->readers->processPaymentIntent(
Okay can you share the request ID for the API request that gives you the error?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Is this what you need POST /v1/terminal/readers/tmr_E0P5xwBFWrL8en/process_payment_intent
or req_FguN6Q3Sus8YEt?
Yeah! Right!
Someone on here suggested that it was "setup incorrectly" and I needed to get it replaced.
It was @odd tangle. In #1030200093304946709-terminal
reaching out for a replacement isn't necessarily a bad idea in this case. With Server-side integrations this should just work (as long as your reader is online).
Created another request req_FguN6Q3Sus8YEt and got the same error. Reader is currently unreachable…
Do you still see the 192 DNS server address?
Yes
Can you change that setting to one of the addresses listed here: 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
In diagnostics it says "DNS resolution: Passed"
We specifically call out which DNS severs to use so I'm suggesting you use those addresses as a next step
So I need to change my local network settings to Cloudflare or Google Public DNS, right?
No
The Wise POS E needs to be able to connect to the global internet. Part of doing that is to use a global DNS server
At least that is how the WPE is configured to work
Ok so if not on the WiFi router that it is using to connect I change that on the Wise POS E? If that's true how?
And doesn't DNS resolution: Passed mean this isn't the issue?
Hi there 👋 taking over for @undone quarry
Ok so if not on the WiFi router that it is using to connect I change that on the Wise POS E? If that's true how?
I don't understand what you're asking here. Can you elaborate?
I @queen niche
And doesn't DNS resolution: Passed mean this isn't the issue?
Not necessarily. I believe it may still say DNS resolution: Passed if it is connecting to a non-global DNS server
Are you seeing the thread
Yup
So, apparently my Wise POS E is not connected to the internet. It shows as connected in the dashboard when I start it. But when I address it with a paymentINtent handoff I get an error saying that the reader cannot be found.
If I request info on the reader it returns this object:
Stripe\Terminal\Reader Object
(
[id] => tmr_E0P5xwBFWrL8en
[object] => terminal.reader
[action] =>
[device_sw_version] =>
[device_type] => bbpos_wisepos_e
[ip_address] => 192.168.86.64
[label] => Accname Main Street
[livemode] =>
[location] => tml_E0P5xwwLGxI3Mb
[metadata] => Stripe\StripeObject Object
(
[oa_accid] => 1
[oa_accname] => accname
[oa_locationid] => 4
)
[serial_number] => WSC513223000030
[status] => offline
)
status => offline
I see that the IP address listed is a local one so I think what we are trying to do is make it so that is not where it looks.
Does the physical device itself show that it is connected to the internet?
Yes
And is your server connected to the same LAN? In other words, are they able to communicate strictly within the LAN?
The server is in a data center in PA.
I'm adding Stripe to an active applicaiton and running a sandbox version prior to deployment
Web application specifically
Okay, got it. Let me dig a bit more on this and circle back in a few
Ok thanks. BTW it was suggested that this device was "not setup properly" and I needed a new one
Who suggested that?
@odd tangle did
@undone quarry suggested "
Can you change that setting to one of the addresses listed here: 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 "
Alright, thanks for that context. I'm going to get another set of eyes here and make sure I'm double-checking my work. I'll circle back in a few minutes
Thanks. Mysterious this one.
Truly
I hope our Connect customers don't have these issues with the readers they purchase.
Is there any firewall on the network that the WPE device is running on?
Nope, unless Google Fibre adds one that I don't know about.
There's zero firewall? I would be surprised if this was the case. Do you know how to check?
Not sure of the relevance (since I'm unsure what your Google Fiber setup/product is), but the below is from: https://support.google.com/fiber/answer/2464928?hl=en:
Both the Network Box and the Network+ Box have four gigabit Ethernet ports where you can plug in computers to get the highest speeds. The Mini Network Box has one Ethernet port. All Network Boxes are equipped with great Wi-Fi, and although Wi-Fi is slower than a wired connection, we have built in an advanced Wi-Fi radio to allow you to get as much speed as possible when you're not wired. Our firewall helps protect your home network from outside hackers without compromising speed.
Hmm. Neither of those are my device.
Got it. No worries. Just checking some preliminary boxes.
I'm looking into the Google fiber thing. It is not like any network I've ever had. Only had it 6 months or so.
On your device, can you go to Settings > Diagnostics > Scroll to the bottom, and take a picture of the result?
Can you scroll to the bottom of that view on the device?
Ah, okay. Thanks for that. Digging some more now
thanks
Alright, so it looks like we have to replace that reader. For some reason this was configured wrong and will need to be replaced (free of charge, obviously). Can you create a support thread using the link below and make sure to mention you were sent by me (two-shoes) on Discord?
This will allow me to pick it up and make sure it gets directly to the people that can replace the device for you.
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
I've started that process already citing karbi but I will include you as well. Thank you
Okay, that works. Sorry to have to chase resolution for so long, only to arrive at the same conclusion, but I figured it was worth making sure all avenues were explored before sending you a new device. We'll likely have you send this device back as well, so we can do a full retro on what went wrong.
Anyway, I'll make sure that thread lands with the right people who can help you get it replaced.