I’m also facing the same issue with my servers; none of them are responding, not even the ones where I keep the default Railway domain.

Hello there! Were you able to resolve this? I’m unable to access the frontend but it looks like its due to the connection not being over https

“”I’m also facing the same issue with my servers; none of them are responding, not even the ones where I keep the default Railway domain. “”

We have documentation that speaks to possible fixes to the application failing to respond issue: https://docs.railway.com/reference/errors/application-failed-to-respond

Could you please check if any of those are helpful to either of you?

@leandrodavimg, if the issue still persists, could you please open a separate ticket for yourself and I’ll help get this resolved for you there as the reasons for the application not responding are usually application specific

I have configured my DNS settings as follows for my domain .werktex.com:

• api.werktex.com CNAME ngbaskend-production.up.railway.app

• www.werktex.com CNAME yruhcg8f.up.railway.app

• @.werktex.com ANAME yruhcg8f.up.railway.app

Despite these settings, I haven't seen the SSL certificate provisioned for my domain.

We only provision certificates for domains in a service if they service has at least one active deploy after the domains are added. The service you linked to this thread has no active deploys.

Could you try getting a deploy up into "Active" state?