Custom domain SSL certificate stuck — DNS verified, cert not provisioning
djp-999
HOBBYOP

a month ago

Domain: www.theshoreacademy.com

Service: the-shore-academy (project the-shore-academy, production)

Project ID: b693589d-4147-476c-bd63-5f790cc08030

The custom domain shows verified in the dashboard — CNAME → fu5dtcqi.up.railway.app and the _railway-verify.www TXT record both show green checks. But the SSL certificate never provisions: TLS handshakes to the domain time out and it serves the *.up.railway.app fallback, while the app itself works fine at the-shore-academy-production.up.railway.app.

I've verified there are no CAA records, DNSSEC is off, there are no conflicting A/CNAME records, and I removed some stale _acme-challenge CNAME records left over from a prior Cloudflare setup. I've redeployed. DNS has been correct and verified for over an hour. I have NOT been repeatedly deleting/re-adding the domain (aware of the Let's Encrypt rate limit).

Could you please re-trigger certificate issuance for this domain from your side? Thank you.

Solved$10 Bounty

Pinned Solution

I’d check your router or firewall settings. Seems like it’s isolated to that network.

Could be a misconfiguration.

15 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 30 days ago


a month ago

Hey, your website is working fine on my end. I also did a nslookup and all your records are correct.

Try clearing your cache and/or flushing DNS. You can also try using another network if possible and/or mobile data, but just waiting a bit should do the trick.

CleanShot 2026-07-22 at 17.21.53@2x.png

Attachments


djp-999
HOBBYOP

a month ago

It is still showing on chrome:

This site can’t provide a secure connection

www.theshoreacademy.com sent an invalid response.

ERR_SSL_PROTOCOL_ERROR


medim

Hey, your website is working fine on my end. I also did a nslookup and all your records are correct. Try clearing your cache and/or flushing DNS. You can also try using another network if possible and/or mobile data, but just waiting a bit should do the trick. ![CleanShot 2026-07-22 at 17.21.53@2x.png](https://station-server.railway.com/attachments/att_01ky5qwamjfexvg64517nf79h8)

djp-999
HOBBYOP

a month ago

Thanks — it does load from mobile, but it's still failing from desktop and other networks. The certificate isn't serving on all your edge nodes. Specifically, connections to 69.46.46.102 (the edge my region resolves to via fu5dtcqi.up.railway.app) accept the TCP connection but hang on the TLS handshake — the server sends no ServerHello and no certificate, so it times out. It works from some nodes and not others, which points to incomplete cert propagation across your edge. Can you force the cert to propagate to all edge nodes / check 69.46.46.102? DNS is verified and unchanged.


djp-999

Thanks — it does load from mobile, but it's still failing from desktop and other networks. The certificate isn't serving on all your edge nodes. Specifically, connections to 69.46.46.102 (the edge my region resolves to via fu5dtcqi.up.railway.app) accept the TCP connection but hang on the TLS handshake — the server sends no ServerHello and no certificate, so it times out. It works from some nodes and not others, which points to incomplete cert propagation across your edge. Can you force the cert to propagate to all edge nodes / check 69.46.46.102? DNS is verified and unchanged.

Try using a VPN. It may be related to an issue with the ISP.


djp-999
HOBBYOP

a month ago

This isn't an ISP or browser issue, and I can prove it from an independent datacenter server (plain openssl/curl, no browser, different network than mine):

Railway edge 69.46.46.61 completes TLS fine and serves the *.up.railway.app cert — so the path to your edge is not blocked.

Every IP fu5dtcqi.up.railway.app (www.theshoreacademy.com) resolves to fails: 69.46.46.102 accepts TCP then hangs the TLS handshake with no ServerHello/cert for SNI www.theshoreacademy.com; 18.204.152.241 hangs for all SNIs (dead node).

It works from some of your edge nodes (your check, mobile) and not others, from multiple independent networks — so the certificate is provisioned on only part of your edge fleet, and this domain is routed to nodes that don't have it.

Please repair/re-propagate the certificate across all edge nodes for this domain, or reassign it off the failing edge target (fu5dtcqi → 69.46.46.102 / 18.204.152.241). I have deliberately not deleted/re-added the domain to avoid the Let's Encrypt rate limit. Can an employee force cert re-propagation on the backend?


djp-999
HOBBYOP

a month ago

still not working


Have you tried using a VPN? Also, what country are you in?


djp-999
HOBBYOP

a month ago

This site can’t provide a secure connection

theshoreacademy.com sent an invalid response.

ERR_SSL_PROTOCOL_ERROR

is there a reason why this keeps happening on chrome on my mac and also iphone


0x5b62656e5d

Have you tried using a VPN? Also, what country are you in?

^


0x5b62656e5d

^

djp-999
HOBBYOP

a month ago

US. I tried using a VPN yes and it works on VPN but want to make sure it is working on my IP


Does it happen on different networks (eg, cellular, or other public WiFi)?


0x5b62656e5d

Does it happen on different networks (eg, cellular, or other public WiFi)?

djp-999
HOBBYOP

a month ago

It will load on different networks seems to be only my mac/wifi problem


So on that specific WiFi, only the Mac has issues accessing the site? Other devices are fine?


0x5b62656e5d

So on that specific WiFi, only the Mac has issues accessing the site? Other devices are fine?

djp-999
HOBBYOP

a month ago

Mac and iphone on same wifi


I’d check your router or firewall settings. Seems like it’s isolated to that network.

Could be a misconfiguration.


Status changed to Solved 0x5b62656e5d 28 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...