a year ago
I've recently deployed my app and some micro services using docker compose. Apparently, all the servers are running as expected as per logs. However, when I try to access one server through public network, I get 404 error. I've tried
https://myservice-production.up.railway.app/http://myservice-production.up.railway.app/ . Also, I added a port number https://myservice-production.up.railway.app:8000/ issues persist
3 Replies
a year ago
Can you point out which application you're trying to see? Do you know what port that application is running on?
You might need to configure your application for ipv6. https://docs.railway.com/guides/private-networking#listen-on-ipv6
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
app is running well thru public url on port 5000. what's not running is icecast2 which is a service to manage playlists. It's configured to run on port 8000, and it's working great locally on localhost:8000
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Hi nd,
I attempted to see what port your service was running on. It doesn't look like port 8000 is actually open and running your application in production.
Additionally, I redeployed your custom dns in attempting to fix it as well, which did not fix the issue. Unfortunately you'll need to go reconfigure your DNS using the following information:
CNAMEicecast2-production.up25219e29.up.railway.app
Status changed to Awaiting User Response Railway • about 1 year ago
a year 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 • 11 months ago