The certificate for your domain was issued this morning and is valid, and TLS now negotiates correctly, so the SSL error you saw is resolved. There is a short window after a new domain is set up before its certificate is in place, and browsers show that exact error during it.

The site is currently unreachable for a different reason. Since your most recent deploy, your container has been refusing the connections our edge forwards to it, so every request returns a 502 before reaching your app. The process itself starts and its scheduled jobs keep running, so the container is up while its web traffic is being refused.

It seams like i cant find the problem, since the domain that is given for free still works.https://addora-production.up.railway.app/

Your custom domain is now returning a 200 and routing correctly through our edge, so the 502 has cleared as well. If your browser still shows an error, try a hard refresh or an incognito window to bypass any cached response.

“The client and server do not support a common SSL/TLS protocol version or cipher suite. The issue was identified while testing on an organization-managed computer with strict security requirements. Could the server be using an outdated TLS protocol or unsupported cipher suite?”