#julesr-terminal-google-mesh
edgy epoch
hello @sonic sierra long time no see. Can I ask you to provide a lot more details about the overall issue, what you see, what's blocking, the error(s) you encounter, etc.
sonic sierra
✋ hey. so i get message Update DNS settings there was a problem resolving local devices with the current settings. Please update your renters DNS servers
after run health check
hollow junco
Hello! I think I know what that might be, give me a few minutes to research...
Ah, here we go. Terminal requires DNS rebinding to work, so I think you need to disable DNS rebinding protection on your network by following these instructions: https://support.google.com/googlenest/answer/9144137?hl=en
@sonic sierra Will you let me know if that works for you or not?
sonic sierra
ok i'll check that but may I ask another question too?
hollow junco
Yep, what's up?
sonic sierra
https://dashboard.stripe.com/test/payments is there a way from payments to show the connect account so we know what payment was what client?
hollow junco
Not on that list view, no, but you can tell by examining the payment details. What workflow are you trying to enable?
sonic sierra
Trying to see in payments where they are from
hollow junco
Can you give me more information? Are you using direct or destination charges?
Sounds like destination if you're looking at this on your platform account?
hollow junco
So if you click on a payment you can see the Transfer destination listed on the detail page.
DNS rebinding is required for Terminal to work when you're using the smart readers and our client-side Terminal SDKs.
If you don't disable that the Terminal readers will not function unless you switch to an entirely different integration, like server-driven.
Here's an example of the destination detail in the Dashboard for a destination payment, which is shown when looking at the detail page of a payment:
