Hi, I'm having intermittent issues with my custom domain after a rocky TLS certificate issuance process.

Project: divine-elegance

Service: frontend

Domain: www.blesni.mk (port 80)

Railway target: eumgqh9o.up.railway.app

Timeline:

Added the custom domain today. Initial TLS certificate issuance failed twice with "Failed to issue TLS certificate - An internal error occurred."

After waiting for DNS propagation to complete (verified via dnschecker.org — CNAME and TXT records fully propagated across all checked regions) and retrying, the certificate was successfully issued (visible in the browser certificate viewer: issued by Let's Encrypt, valid Aug 10 – Nov 8 2026, correct CN = www.blesni.mk).

However, since then the domain has been intermittently inaccessible. Sometimes it loads correctly over HTTPS with no warnings. Other times it shows ERR_CONNECTION_REFUSED, and earlier I also saw ERR_CERT_COMMON_NAME_INVALID in the network log even though the certificate itself is valid. This happens both in regular browser windows and fresh incognito sessions, so it doesn't appear to be local caching.

The underlying app is fully healthy — it loads perfectly and consistently via the auto-generated Railway URL (distinguished-tenderness-production-7e42.up.railway.app).

Could you check if there's an issue with edge routing/caching for this custom domain, possibly left over from the earlier failed certificate attempts? I'd appreciate help stabilizing this — I'm launching this platform to real students in about 10 days.

Thanks!