13 days ago
Hello, app.gomindy.fr, attached to the gomindy-app service in the bilans environment of the Gomindy project, remains on "Issuing TLS certificate".
The public CNAME points to uihpc8kz.up.railway.app and the TXT record _railway-verify.app.gomindy.fr is published. The Railway-generated domain works, but the custom domain returns ERR_CERT_COMMON_NAME_INVALID.
Could you please check domain validation and retry certificate issuance if necessary?
1 Replies
Status changed to Awaiting Railway Response Railway • 13 days ago
13 days ago
The certificate for your custom domain has now been issued and the domain is verified, so the certificate error should be gone. The domain now returns a 502 "Application failed to respond" because its target port is set to 3000. Your app starts with next start --port $PORT, and your working Railway-generated domain has no fixed port, so it auto-detects the port the app actually listens on. In the gomindy-app service's Settings, under Networking, edit the custom domain and change its target port to the port your app listens on (the same one the generated domain uses), or clear it so it auto-detects.
Status changed to Awaiting User Response Railway • 13 days ago
6 days 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 • 6 days ago