a month ago
Hey guys,
I set up a Cloud Flare tunnel. The tunnel is working when I use public and domain. Everything works fine, however when I try to set up the Cloud Flare tunnel to work with the internal Railway provided domain name, then I get a 502 error. This most likely indicates that either that something is incorrectly set up, but overall everything works, so I think the issue lays in one setting not set correctly. But I followed the tutorial, and everything looked to be correct.
I think it correctly done as stated in the tutorial. https://railway.com/deploy/cf-tunnel
And as earlier mentioned, when I put any type of publicly available domain, so for example I put there https://google.com or something, then everything works. The thing is that I don't want to assign a public available domain because it's a staging environment.
3 Replies
a month ago
Hey there! We've found the following might help you get unblocked faster:
🧵 502 Bad Gateway after successful container start — Gunicorn running but Railway edge not routing
🧵 Can’t reach Next.js service from other containers using internal URL (only works with public URL)
If you find the answer from one of these, please let us know by solving the thread!
a month ago
I tried without port, with port 3001 8080 and 3000, tried https also, all same issue
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • about 1 month ago