2 months ago
Unable to access deployed site from today 12 Jan 2026
Deployment logs:
Starting Container
[2026-01-12 17:04:37 +0000] [1] [INFO] Starting gunicorn 23.0.0
[2026-01-12 17:04:37 +0000] [1] [INFO] Listening at: http://0.0.0.0:8080 (1)
[2026-01-12 17:04:37 +0000] [1] [INFO] Using worker: sync
[2026-01-12 17:04:37 +0000] [2] [INFO] Booting worker with pid: 2
Stopping Container
Github repo link: https://github.com/tankaria926/tankaria
branch: main
12 Replies
2 months ago
The github link, https://github.com/tankaria926/tankaria, is not found. I guess it is not public
aldrinm
The github link, https://github.com/tankaria926/tankaria, is not found. I guess it is not public
2 months ago
its private repo
2 months ago
Its showing below error while accessing
This site can’t be reached
Check if there is a typo in tankaria-production.up.railway.app.
If spelling is correct, try running windows network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
It was working till yesterday.
Note: no code changes are done
2 months ago
Do you have this set to serverless?
Have you set the port to 8080 for the railway.app domain?
random_username
Do you have this set to serverless?Have you set the port to 8080 for the railway.app domain?
2 months ago
tankaria-production.up.railway.app
port 8080
2 months ago
Have you tried flushing DNS cache? I can access the site just fine.
Attachments
0x5b62656e5d
Have you tried flushing DNS cache? I can access the site just fine.
2 months ago
why cache clear is needed ?
without cache clear, other sites are working
is this issue with railway.com or any specific reason ?
2 months ago
Local DNS cache.
Previously, when you tried accessing the website, your machine probably couldn't find it, so right now, it'll assume it still can't find it.
Flushing the DNS cache may fix this issue by making the machine forget about the fact that it couldn't find where the URL was pointing to, forcing it to search where the URL points to again.
Status changed to Open brody • about 2 months ago
2 months ago
I followed steps mentioned on https://www.youtube.com/watch?v=2AZhdwHcMxY for cache and it got resolved
Thanks !
Status changed to Solved tankaria926 • about 2 months ago
0x5b62656e5d
Local DNS cache.Previously, when you tried accessing the website, your machine probably couldn't find it, so right now, it'll assume it still can't find it.Flushing the DNS cache may fix this issue by making the machine forget about the fact that it couldn't find where the URL was pointing to, forcing it to search where the URL points to again.
2 months ago
still today its giving same error
This site can’t be reached
Check if there is a typo in tankaria-production.up.railway.app.
If spelling is correct, try running windows network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Open brody • about 2 months ago
2 months ago
Have you got your application set to serverless? If yes it could be spinning up the instance during that time
Also try another browser when testing, I've just tested and I can access it fine.
Attachments
2 months ago
Pretty sure a sleeping server wouldn't give a NXDOMAIN error.
The browser would probably just time out/return a invalid response error if the deployment was sleeping.
NXDOMAIN means the machine couldn't find where the domain is pointing to.