15 days ago
Hi Railway Support,
I'm experiencing an SSL issue with my production custom domain hosted on Railway.
My application was working correctly until November 5, 2026, but the production domain is now returning a Cloudflare Error 526 (Invalid SSL Certificate).
Here are the details:
Production domain: https://www.azurio.com.ar (also accessible through https://azurio.com.ar)
Test domain: https://test.azurio.com.ar
Railway production URL: https://azurio-frontend-production.up.railway.app
Cloudflare SSL mode: Full (strict)
Current behavior:
The test environment works correctly through Cloudflare.
The production custom domain returns Error 526.
The production application works correctly through the Railway-generated public URL.
The frontend and backend are operational, and authentication works.
Railway detects the Cloudflare proxy on the production custom domain.
I noticed the ongoing Railway networking incident involving IP addresses being blocked by security providers.
Could this incident be affecting SSL certificate validation between Cloudflare and Railway?
Could you please check whether Railway is correctly serving a valid SSL certificate for my production custom domain, including its renewal and provisioning status?
I'd prefer to keep Cloudflare's Full (strict) mode enabled for security reasons.
Thank you for your help!
1 Reply
15 days ago
The 526 has nothing to do with the IP-blocking incident. We don't have a valid certificate for your production www domain yet: its certificate is still being issued and hasn't completed. The root domain isn't added to the service at all, so we can't serve a certificate for it.
To complete issuance, our certificate check has to reach your service over plain HTTP. Right now that request gets a 403 from Cloudflare and never reaches us. Look for a Cloudflare security rule, WAF rule, or bot setting that blocks HTTP requests to this hostname, especially requests under the /.well-known/acme-challenge/ path, and allow that traffic through. You can also switch the record to DNS only (grey cloud) until the certificate is issued.
Also make sure the www record is a CNAME pointing to the exact target shown for that domain under the service's Settings → Networking. We can't currently see that CNAME behind the proxy.
Once the certificate is issued, you can turn the proxy back on and keep Full (strict). If you want the root domain to work too, add it to the service as its own custom domain and follow the records it shows. Root domain setup explains the CNAME flattening requirement.
Status changed to Awaiting User Response Railway • 15 days ago
8 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 • 8 days ago