21 days ago
I have many users reporting this. restarting their router fixes it but the amount of users hitting this is way too high. I can't find anything I'm doing that is wrong so I'm thinking it's railway.
Attachments
1 Replies
21 days ago
The SSL_ERROR_RX_RECORD_TOO_LONG error is caused by a stray A record (69.46.46.55) on standard-reader.app that is overriding the CNAME Railway auto-configured for it. Traffic hitting that A record reaches a server that doesn't serve the correct TLS certificate, which triggers the SSL error in Firefox. Users who restart their router flush their DNS cache and may briefly get the correct resolution, which is why the restart "fixes" it. Go to your workspace domains page, open standard-reader.app, and remove the A record pointing to 69.46.46.55 so that only the CNAME to Railway's edge remains. Once removed, all users will resolve to Railway correctly after their DNS caches expire (usually within minutes to hours).
Status changed to Awaiting User Response Railway • 21 days ago
14 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 • 14 days ago