10 months ago
Hi everyone ^^
Really easy setup. Two websites, one caddy reverse proxy.
Site is reachable on 8080 via public domain just fine:
https://web-production-8574c.up.railway.app/
But trying to get any routing from the reverse proxy fails.
I ssh'd into the reverse proxy service, pinging the internal route works fine, calling a wget against the internal route and port does not - simply runs into a timeout / never returns (see screenshot).
I know there is only IPv6 routing for private networking (even though now there is an information, that IPv4 is also available?). But neither :: nor 0.0.0.0 worked when starting the app (Nitro based server / Tanstack start).
Any pointers? 🙏
7 Replies
10 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
10 months ago
Hello,
This is caused by a known issue with IPv4 private networking that is currently being worked on.
Some packets outright get dropped.
Until we have a fix for this, please disable that flag and create a new project, then recreate the project from scratch.
Thank you. It helped to use [web.railway.internal] instead of web.railway.internal for now. Thank you very much 🙏
10 months ago
Not sure of the relevance of that; how you use the domain does not change the packets that get dropped.
10 months ago
!s
Status changed to Solved brody • 10 months ago
10 months ago
✅ The ticket Packet loss in Private Networking has been marked as completed.
10 months ago
Hello,
Update here: The previously mentioned issues with IPv4 private networking have been fixed. However, you will need to redeploy the affected services.
Status changed to Awaiting User Response Railway • 10 months ago
10 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 10 months ago