无法访问网站(ERR_TOO_MANY_REDIRECTS)及DNS异常问题求助
Hey there, let's work through this issue step by step—sounds like a mix of DNS propagation delays, SSL misconfigurations, and mixed content headaches. Here's what to check and fix:
1. 确认Cloudflare DNS已完全生效
Since you just switched back to Cloudflare's nameservers, DNS propagation might still be in progress. Verify this with a quick terminal check:
- Run either command:
dig pro-cs-is.com NSornslookup -type=NS pro-cs-is.com - Look for Cloudflare's official nameservers (like
ns1.cloudflare.com,ns2.cloudflare.com) in the output. If you still see GoDaddy's nameservers, wait a bit longer (DNS TTL can take up to 24 hours in rare cases, but usually resolves in minutes) or double-check that you saved the Cloudflare NS records correctly in GoDaddy's dashboard.
2. Fix the net::ERR_TOO_MANY_REDIRECTS Error
This is almost always a mismatch between Cloudflare's SSL settings and your origin server's SSL setup:
- Go to your Cloudflare dashboard → SSL/TLS → Overview
- If your origin server has a valid, trusted SSL certificate: Set the encryption mode to Strict (this ensures Cloudflare only connects to your origin over HTTPS, avoiding loops).
- If your origin doesn't have an SSL certificate (or uses a self-signed one): Set the mode to Flexible, but make sure your origin server isn't forcing HTTPS. Check your
.htaccess(for Apache) or nginx config for redirect rules that push traffic to HTTPS—those will create a loop with Flexible mode.
- Also confirm that Cloudflare's Universal SSL certificate is active in the SSL/TLS → Edge Certificates section.
3. Resolve Mixed Content Errors
The "Mixed content tests failed" message means your site is loading some resources (images, scripts, stylesheets) over HTTP while the main site uses HTTPS. Here's how to fix it:
- Use your browser's DevTools (press F12) → Console tab to spot exactly which resources use HTTP links. Update those in your site's code to use HTTPS or relative paths (e.g.,
/images/logo.pnginstead ofhttp://pro-cs-is.com/images/logo.png). - For a quick fix without editing code, enable Automatic HTTPS Rewrites in Cloudflare's SSL/TLS → Edge Certificates section. This feature automatically rewrites HTTP links to HTTPS on the fly, resolving most mixed content issues instantly.
4. Clear Stale Caches
Cached data might be keeping old settings alive:
- Clear your browser's cache and cookies, or test the site in Incognito/Private mode.
- Purge Cloudflare's cache from the dashboard → Caching → Configuration → Purge Cache (select "Purge Everything" to clear all cached content).
Give these steps a shot, and let me know if you run into any roadblocks!
内容的提问来源于stack exchange,提问作者MML

