Page rules subdomain
Hello all,
I try to redirect www.app.domain.co to app.domain.co
What I have
- Domain name on another registrar
- NS/DNS on Cloudflare
- Website hosted outside of Cloudflare
- I use autogenerated Cloudflare's SSL only, without extra configuration
What I did
- Rules -> Page Rules -> Create Page Rule
- Forwarding URL (301)
- Made me add an A entry on www.app., to 192.0.2.1 (kind of as a place holder if I got it right ?)
My rule looks like this :
www.app.domain.co/*
Forwarding URL (Status Code: 301 - Permanent Redirect, Url: https://app.domain.co)
Result
DNS_PROBE_FINISHED_NXDOMAIN on Vivaldi
ERR_SSL_VERSION_OR_CIPHER_MISMATCH on Chrome
SSL_ERROR_NO_CYPHER_OVERLAP on FireFox
What did I do wrong ^^" ?
Looks like it's SSL related but... I don't really see what to do from here
Thanks 🙂
5 Replies
Support AI
Based on the provided documentation, it seems like you're experiencing a redirect loop between Cloudflare and your origin server. The error messages you're seeing (DNS_PROBE_FINISHED_NXDOMAIN, ERR_SSL_VERSION_OR_CIPHER_MISMATCH, and SSL_ERROR_NO_CYPHER_OVERLAP) are likely related to the redirect loop.
According to the Cloudflare documentation (https://community.cloudflare.com/t/849592), the error "Too Many Redirects" or "ERR_TOO_MANY_REDIRECTS" indicates a redirect loop between Cloudflare and your origin server. The suggested fix is to remove the redirect on your origin server.
In your case, you've set up a Page Rule to forward www.app.domain.co to app.domain.co, but you also have an A record for www.app.domain.co pointing to 192.0.2.1. This might be causing the redirect loop.
To resolve the issue, you can try removing the A record for www.app.domain.co and instead, set up a CNAME record for www.app.domain.co to point to the same CNAME record as app.domain.co. This should allow the redirect to work correctly.
Additionally, you can also try checking the SSL/TLS settings for your domain on Cloudflare to ensure that the SSL certificate is properly configured.
Please refer to the Cloudflare documentation (https://developers.cloudflare.com/support/third-party-software/others/configure-cloudflare-and-heroku-over-https/) for more information on configuring SSL/TLS settings.
If you continue to experience issues, you can try checking the troubleshooting suggestions in the Cloudflare Community Tip (https://community.cloudflare.com/t/849592) for more detailed options.
Sources
This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.
www.app.domain.co is a second-level domain so isn't covered by the Universal SSL certificate (which covers only example.com and *.example.com). You can use an Advanced Certificate to generate certificates for 2nd level and deeper subdomains, or just don't use the www.
https://developers.cloudflare.com/ssl/edge-certificates/advanced-certificate-manager/Cloudflare Docs
Advanced certificates
Use advanced certificates when you want something more customizable than Universal SSL but still want the convenience of SSL certificate issuance and renewal.
I was hoping the certificate wouldnt be necessary for a redirect :/
Sadly it's a legacy subdomain that I have to redirect... looks like the only option is to pay for the advanced certificate since I'm on the free version ?
Thanks a lot for your help ^^
The SSL certificate is still needed for a redirect. There is a cheeky workaround. Create a Pages project and add a custom domain
www.sub.example.com for it which will create a certificate, you can redirect using the HTML or with redirect rules to sub.example.com so you can capture those users clicking www links, as here...
https://community.cloudflare.com/t/installed-cloudflare-and-the-site-is-fine-but-none-of-the-subdomains-work-with-www/856274/7?u=sjrI have tons of projects on cloudflage pages I know exactly what you mean, what a clever idea XDXD
I'll do that for now and "force" the client to choose between paying the advance certificate or droping the www by the end of the year
thanks a lot !