7 days ago
Hello Team,
I am having an issue deploying my custom domains astrolinux.net and www.astrolinux.net on my service astrolinux-engine.
The automated "Railway AI Agent" previously attempted to fix it via the API, but it ended up misconfiguring a TCP Proxy on port 5432 and generating some ghost domains (like astrolinux-engine-production-95b4.up.railway.app and -daf3) which broke the service network state. I have tried deleting and re-adding the custom domains, but the edge proxy is still failing.
Current Status & Technical Specs:
DNS Status: The apex domain astrolinux.net and www are fully propagated globally, strictly pointing to Railway's edge IP (69.46.46.53).
Application Port: The container is running a Flask app listening correctly on port 8080.
The Error: Running curl -Iv http://astrolinux.net correctly returns an edge-managed 301 Moved Permanently to HTTPS. However, running curl -Ik https://astrolinux.net immediately drops with an HTTP/2 404 and the header x-railway-fallback: true from server: railway-hikari.
The dashboard UI is permanently stuck on "Waiting for DNS update". It seems the Let's Encrypt SSL generation process is completely frozen in your edge queue due to the previous conflicting states.
Could you please:
Manually trigger the DNS verification and force the SSL certificate generation for both astrolinux.net and www.astrolinux.net.
Clear any ghost domains or stuck TCP proxies (like the 5432 config) generated by the AI agent on this service.
Thank you very much for your time and help!
Pinned Solution
7 days ago
For your root domain astrolinux.net, you need to add a TXT record for _railway-verify.astrolinux.net. If you are using the API to add your custom domain, you can find it in verificationToken under status.
The domain www.astrolinux.net works just fine. If you are having issues accessing it, it might be related to caching issues. Accessing it from an incognito tab or using a different network should help.
Attachments
2 Replies
7 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 7 days ago
7 days ago
For your root domain astrolinux.net, you need to add a TXT record for _railway-verify.astrolinux.net. If you are using the API to add your custom domain, you can find it in verificationToken under status.
The domain www.astrolinux.net works just fine. If you are having issues accessing it, it might be related to caching issues. Accessing it from an incognito tab or using a different network should help.
Attachments
darseen
For your root domain `astrolinux.net`, you need to add a TXT record for `_railway-verify.astrolinux.net`. If you are using the API to add your custom domain, you can find it in `verificationToken` under `status`. The domain `www.astrolinux.net` works just fine. If you are having issues accessing it, it might be related to caching issues. Accessing it from an incognito tab or using a different network should help. 
7 days ago
"Thank you so much, darseen! That was exactly the issue. The TXT record host was misconfigured on my end. I fixed it to _railway-verify and updated the CNAME, and now everything is up and running perfectly with an HTTP 200 OK. Appreciate your help!"
Status changed to Open medim • 6 days ago
Status changed to Solved medim • 6 days ago