a year ago
Hello Railway Support,
I am running Vault and PostgreSQL inside Railway and connected them using Tailscale. The services are only reachable via internal IPv6 hostnames (e.g. vaultxxxx.railway.internal).
Tailscale itself starts correctly and I can ping the container from my workstation using its Tailscale IP (e.g. 100.x.x.x). However, inside the container I cannot connect to the internal Railway IPv6 URLs anymore. Yesterday this was still working fine, but today it suddenly stopped.
This behavior seems strange — have you seen similar cases before?
Thanks in advance!
1 Replies
a year ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Internal Networking Issue: Prometheus Cannot Connect to Django App Despite Correct Configuration
- 🧵 Can't find root of 502 errors on external calls
- 📚 Using the CLI
If you find the answer from one of these, please let us know by solving the thread!
Status changed to Solved autodynation • 11 months ago