ERR_TOO_MANY_REDIRECTS means the browser is trapped in a redirect loop. The fastest fix depends on where the loop is created. Open the URL in a private window or another browser first. If it works there, clear cookies and site data for the affected domain. If it fails in multiple browsers, inspect the redirect chain and correct the Cloudflare, proxy, load-balancer, web-server, tunnel, or CMS rules that send the request back to an earlier URL.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What ERR_TOO_MANY_REDIRECTS means
A normal redirect sends a browser from one URL to another and ends with a page. This error appears when the browser receives redirects indefinitely or reaches the browser’s redirect limit without getting a final response. Cloudflare describes the condition as visitors becoming stuck in a redirect loop.
As an Amazon Associate I earn from qualifying purchases.
The loop can involve different layers:
- Your browser’s cookies or stored site state.
- A CDN or reverse proxy such as Cloudflare.
- An HTTPS policy, HSTS setting, or edge redirect.
- A load balancer that terminates TLS.
- Apache, Nginx, or another origin web server.
- Application middleware, a CMS, or a redirect plugin.
- A Cloudflare Tunnel service URL.
Do not assume that clearing the browser is the universal answer. It only addresses contradictory client-side state; a server-side loop will continue for every visitor until the configuration changes.
Cloudflare’s troubleshooting documentation, updated September 1, 2026, states: “This error occurs when visitors get stuck in a redirect loop.”
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
First determine whether the problem is local or site-wide
Test a private window
- Copy the complete failing URL.
- Open a private or incognito window.
- Paste the URL and load it without using an old bookmark.
If the page works privately, the original browser probably has stale or conflicting cookies, login state, or other stored data for that domain. Delete data for that site only, close the affected tabs, reopen the browser, and try again. A site-specific reset is safer than deleting every browser cookie.
Test another browser or network
Try a second browser or a different connection. If only one browser fails, concentrate on its stored state and extensions. If several browsers and users fail on the same URL, treat the problem as a site configuration issue. A phone on cellular data is a useful comparison when you suspect a local proxy, corporate gateway, or security appliance.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Record what actually fails
Write down the exact hostname, scheme, path, and whether the failure occurs after login. A loop limited to an administration path can have a different cause from a loop affecting the home page. Preserve the time of the test and the browser result so a site administrator can compare it with server and proxy logs.
Inspect the redirect chain before changing settings
Every redirect response normally contains a Location header. The destination in that header reveals which rule is sending the request back.
Use browser developer tools
- Open developer tools and select the Network panel.
- Enable recording, clear the existing entries, and reload the failing URL.
- Click each 301, 302, 307, or 308 response.
- Read its
Locationheader and note the request URL, response status, and scheme.
Stop after you have recorded a repeating sequence. Do not keep reloading a loop indefinitely, because it can create noisy logs and repeated authentication requests.
Use a command-line header request
From a terminal, request headers without following redirects:
curl -I https://example.com
To follow the chain while displaying every response, use:
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
curl -IL --max-redirs 20 https://example.com
For a compact header dump that does not download the page body:
curl -s -D - -o /dev/null https://example.com
Replace the example host with the affected hostname. Look for these patterns:
| Observed pattern | Likely conflict | Where to investigate |
|---|---|---|
http:// alternates with https:// |
HTTPS enforcement disagrees between proxy and origin | Cloudflare SSL/TLS mode, origin redirects, load-balancer forwarded-protocol handling |
Apex host alternates with www |
Two canonical-host rules point at each other | Edge Redirect Rules, legacy Page Rules, web-server host rules, CMS URL settings |
| Two paths alternate | Application or rewrite rules redirect each path to the other | CMS plugins, middleware, Apache/Nginx rewrites, route configuration |
| Login repeatedly returns to login | Cookie, secure-cookie, session, or canonical-URL mismatch | Browser cookies, CMS settings, proxy HTTPS detection, authentication middleware |
A loop that alternates schemes is usually a protocol problem. A loop that alternates hostnames or paths is usually a conflicting redirect rule.
Match Cloudflare SSL/TLS mode to the origin
When Cloudflare sits between visitors and your server, there are two connections: the visitor-to-Cloudflare connection and the Cloudflare-to-origin connection. The SSL/TLS mode controls the second connection. The origin’s own redirects must agree with it.
| Cloudflare mode | Connection from Cloudflare to origin | Typical loop condition | Corrective action |
|---|---|---|---|
| Flexible | HTTP | The origin forces every HTTP request to HTTPS. Cloudflare sends HTTP again, receives the redirect, and repeats the cycle. | Remove the origin HTTPS redirect, or raise Cloudflare encryption to Full or Full (strict) after installing a suitable origin certificate. |
| Full | HTTPS, without strict certificate validation | The origin redirects an HTTPS request back to HTTP, while edge settings keep sending visitors to HTTPS. | Remove the origin rule that changes HTTPS back to HTTP and keep the request on HTTPS. |
| Full (strict) | HTTPS with certificate validation | The same HTTPS-to-HTTP redirect conflict can loop. A separate certificate problem may produce a TLS error rather than a redirect error. | Keep the origin on HTTPS and use a certificate that satisfies strict validation. |
Fix a Flexible-mode loop
In Flexible mode, an HTTPS visitor request reaches Cloudflare over HTTPS, but Cloudflare contacts the origin over HTTP. If the origin automatically changes HTTP to HTTPS, Cloudflare receives a redirect to the same public HTTPS URL and repeats the request over HTTP. This is the classic Flexible loop.
- Confirm the current mode in the Cloudflare dashboard under SSL/TLS.
- Check the origin’s HTTP virtual host, Apache or Nginx configuration, load balancer, and application middleware for an unconditional HTTP-to-HTTPS redirect.
- Either remove that origin redirect while Flexible is in use, or install and verify an origin certificate.
- Change the mode to Full or Full (strict), depending on the certificate and validation requirements.
- Retest in a private window and inspect the headers again.
Do not leave the origin rule and Flexible mode in place together. They describe opposite expectations about the protocol used between Cloudflare and the server.
Fix a Full or Full (strict) loop
Full modes make an HTTPS connection to the origin. If the origin then redirects that HTTPS request to HTTP, an edge rule may send the visitor back to HTTPS, creating an inverse loop.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
- Check the origin’s HTTPS virtual host and application code for redirects targeting an
http://URL. - Remove or revise that redirect so an HTTPS request remains HTTPS.
- Check canonical-host rules so they do not change both scheme and hostname in opposing directions.
- Verify that the origin certificate is valid for the hostname when using Full (strict).
Full and Full (strict) require an origin certificate; Full (strict) additionally validates that certificate. Changing modes without correcting the redirect logic only moves the failure to another layer.
Review Cloudflare edge certificates and redirect rules
Always Use HTTPS
In SSL/TLS → Edge Certificates, inspect Always Use HTTPS. This setting redirects HTTP visitors to HTTPS at the edge. It can participate in a loop if the origin receives HTTPS and redirects it back to HTTP. Keep it enabled only when the origin and application support an HTTPS end state.
HSTS
Review HSTS settings in the same area. HSTS tells compatible browsers to use HTTPS for future requests, so it should be enabled only after every required hostname and subdomain works correctly over HTTPS. HSTS does not replace a correct origin configuration and is not a substitute for fixing a redirect cycle.
Redirect Rules and legacy Page Rules
List every active redirect in Rules → Redirect Rules and any remaining legacy Page Rules. Look for a pair such as:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →https://a.example.comredirects tohttp://b.example.com.http://b.example.comredirects back tohttps://a.example.com.
Also check rules that match a broad pattern and unintentionally catch the destination of another rule. Temporarily disable one suspected rule, test the chain, and then replace it with a single canonical rule rather than leaving overlapping rules disabled indefinitely.
Check HTTPS enforcement guidance
Cloudflare’s HTTPS-enforcement guidance recommends evaluating redirects at both the origin and the dashboard, avoiding forwarding targets that begin with http, confirming that SSL mode is not Off, and enabling Always Use HTTPS only when the complete application supports HTTPS. Apply those checks to every hostname that can appear in the chain, including redirects for old domains.
Correct the origin server and load balancer
After edge settings are consistent, inspect the server that ultimately generates the response.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Apache and Nginx
- Search virtual-host or server-block files for duplicate HTTP-to-HTTPS redirects.
- Check rewrite conditions that use the wrong host, port, or forwarded scheme.
- Remove rules that send HTTPS traffic to HTTP.
- Confirm that canonical
wwwor apex-host rules point in one direction only.
Make one configuration change at a time and reload the web server using your normal, documented service procedure. Keep a copy of the previous configuration so you can restore it if another route breaks.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsApplications and middleware
Framework middleware often decides whether a request is secure before the route handler runs. If a proxy terminates TLS but the application does not trust the forwarded-protocol information, the application may believe every request is HTTP and redirect forever. Configure the trusted proxy and forwarded-protocol handling according to the framework’s documentation, then verify that an HTTPS request is recognized as secure in application logs.
This diagnosis is an implementation inference from the proxy/origin loop pattern; verify it in the actual server and application configuration rather than changing headers blindly.
Load balancers
Check where TLS terminates. If the load balancer receives HTTPS and forwards HTTP internally, the application must be told that the original client scheme was HTTPS. Conversely, do not force an internal redirect to HTTPS if the proxy already supplies the correct secure context. Ensure health-check URLs are excluded from authentication redirects so they do not hide the real response during testing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix Cloudflare Tunnel protocol mismatches
Cloudflare Tunnel deployments have another documented failure mode. An origin may redirect HTTP requests to HTTPS while the published application route uses an http:// service URL. The tunnel repeatedly reaches the origin over the protocol that the origin rejects.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Open the tunnel’s published application route.
- Record the service URL scheme and port.
- Compare it with the protocol the origin expects.
- Change the service URL or the origin redirect behavior so both sides use the intended protocol.
- Test the public hostname from a clean browser session and inspect the complete chain.
Do not fix a tunnel loop by adding another public redirect. The published service and origin must agree on the protocol first.
WordPress and other CMS sites
Compare the public URLs
For WordPress, compare the WordPress Address (URL) and Site Address (URL) with the public HTTPS hostname. They must use the intended scheme and canonical host. A mismatch such as an HTTPS public site paired with an HTTP home URL can cause repeated canonical redirects, especially when a proxy is in front.
Isolate plugins and themes
- Record which redirect, SSL, and caching plugins are active.
- If the loop began after a change, disable the most recently changed component first.
- Test the front end and login separately.
- Restore components one at a time until the conflicting rule is identified.
Cloudflare specifically recommends its WordPress plugin and Automatic HTTPS Rewrites to reduce redirect-loop and mixed-content problems. These tools cannot correct an origin that deliberately redirects HTTPS back to HTTP, so verify the underlying protocol settings as well.
Other CMS platforms
Look for equivalent settings named base URL, canonical URL, force SSL, or trusted proxy. Disable duplicate redirect features in the CMS, web server, and proxy rather than enabling all of them. Keep one authoritative rule for HTTPS and one for canonical-host selection.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose the smallest effective fix
The right change depends on where the first incorrect redirect appears.
| Where the loop starts | Preferred action | Scope and risk |
|---|---|---|
| One browser only | Delete cookies and site data for the domain, close tabs, and retry. | Narrow, reversible client change; does not affect other visitors. |
| Cloudflare edge | Align SSL/TLS mode, Always Use HTTPS, HSTS, Redirect Rules, and Page Rules. | Affects all visitors and hostnames covered by the rules. |
| Tunnel route | Match the published service URL scheme to the origin’s expected protocol. | Changes the tunnel application route. |
| Load balancer or proxy | Correct TLS termination and forwarded-protocol trust. | Can affect every application behind that listener. |
| Origin server or CMS | Remove duplicate redirects and make the canonical scheme and host unambiguous. | May affect application routes, login, APIs, and cached responses. |
Verify that the loop is gone
- Clear or bypass the affected browser’s stored site data, then open a private window.
- Request the original URL and record every status and
Locationheader. - Confirm that the chain ends with a final response such as
200 OK, or with one intentional redirect followed by the expected page. - Test both HTTP and HTTPS entry points if HTTP remains publicly reachable.
- Test the apex and
wwwhostnames, old paths, login, and any API endpoint that previously failed. - Repeat from another browser or network to ensure the fix is not limited to one client.
Keep the final redirect chain as a deployment check. If a future HTTPS, domain, CDN, or CMS change reintroduces a loop, comparing the new headers with the known-good chain usually identifies the responsible layer quickly.
When to contact the site administrator
A visitor cannot correct a site-wide loop by changing browser settings. Send the administrator the failing URL, time of failure, browser and network tests, and a short redirect trace showing the repeating URLs. Mention whether the sequence alternates HTTP and HTTPS, hostnames, or paths. Avoid sending passwords, session cookies, or authorization headers.
Site owners should involve the hosting or infrastructure team when they lack access to the Cloudflare account, tunnel configuration, load balancer, or origin server. The essential question is not merely “which redirect should be removed?” but “which layer owns the canonical protocol and hostname?” Once one layer is authoritative and every other layer honors it, the loop ends.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
