Everything works great locally. Deploy it and works get again. Add a VPN, put yourself on the other side of the planet and all requests to the graphql endpoint fail. It seems like, if server is in Europe, and you make a request from Europe it's all good. Long round-trip? Error. Any clues 🕵️♂️ ?
Last active 3 months ago
6 replies
11 views
- MM
Everything works great locally.
Deploy it and works get again.Add a VPN, put yourself on the other side of the planet and all requests to the graphql endpoint fail.
It seems like, if server is in Europe, and you make a request from Europe it's all good. Long round-trip? Error.
Any clues 🕵️♂️ ?
- DA
might be interesting to try to use tcpdump to see what’s happening. However, keep in mind that by using a VPN and putting yourself “on the other side of the world” your traffic has to go to the VPN, from there to nhost, then back to the VPN and then back to you so you are potentially getting yourself an RTT of ~1s
- DA
a more realistic test would be to get a VM or similar on the other side of the world and make a request from it rather than using a VPN
- DA
it could also be an MTU issue somewhere, VPNs are notorious for that
- DA
you could try lowering the MTU on your machine and see if that makes it work (probably a setting on your VPN client)
- MM
Thanks for the insight 🙏
Some of our Thai customers reported "things not working". VM's based in Europe. Using a VPN was a naive way to see what was going on.
Last active 3 months ago
6 replies
11 views