English
Magyar
What if your website is inaccessible not because of a server outage, but due to a misconfigured redirect? The ‘too many redirects’ error can prevent visitors – and even you, when trying to log in to the WordPress admin panel – from opening the site. The browser message alone does not reveal whether the problem lies with your device or with the website’s settings.
A redirect loop occurs when two or more rules successively send the browser from one address to another, and then back to the previous one. This can be caused, for example, by data stored in the browser, WordPress URL settings, a plugin, the .htaccess file or the HTTPS configuration. Making changes at random may further impair the site’s accessibility, so you should first isolate the possible causes.
In this guide, we’ll proceed in a logical order: first, we’ll check your browser, then your WordPress settings, plugins and redirect rules. We’ll also show you when it’s appropriate to request a hosting or server-side investigation, so that you can resolve the issue in a targeted manner and avoid unnecessary changes.
What does the ‘too many redirects’ error mean, and why does it occur?
The ‘too many redirects’ error appears when, upon opening a web address, the browser encounters redirects that do not lead to a final page. The message indicates that the request has failed, but does not in itself prove that the browser is faulty or that the website’s entire system has crashed. The cause may be local, such as a stored cookie, but is often to be found in the website’s or server’s settings.
A redirect loop is caused by repeated changes of address: a request is sent from one URL to another, which then redirects back to the original address. A common example is when the system attempts to redirect the visitor to both the ‘www’ and non-‘www’ versions of the address at the same time. This can happen on any website, not just WordPress sites.
How does a redirect loop work?
Let’s assume that the URL http://pelda.hu redirects to HTTPS, whilst the rule for https://pelda.hu requests the version with ‘www’, where another setting then redirects the browser to the URL without ‘www’. The request thus keeps being sent to different URLs over and over again. The browser does not receive the final page content, so after a while it stops trying and displays an error message. The maximum number of redirects allowed may vary depending on the browser.
Where might too many redirects occur?
To troubleshoot the issue, isolate the layers that may contain settings affecting redirection or the request path. The same symptom may originate from several sources, so the browser message alone does not identify the root cause.
- Browser: stored cookies or cached data may prevent the page from loading. If the website works when accessed from a different browser or in incognito mode, please try this option as well.
- WordPress: the WordPress address and the website address may differ, for example, in terms of HTTP/HTTPS or the ‘www’ prefix. A plugin may also trigger a redirect that conflicts with other settings on the site.
- Server configuration: rules set on the hosting server, such as redirects in the Apache .htaccess file or in the Nginx settings, may conflict with WordPress’s own rules.
- DNS: the DNS server directs the domain name to the correct server, but does not perform HTTP redirection itself. However, in the event of an incorrect record or one pointing to a different destination, the request may reach a server where different redirection rules apply.
The redirect set up on the hosting account is included in the server’s response, whilst a redirect initiated by the website itself may be triggered, for example, by WordPress or a plugin. Both layers can function correctly on their own, but together they can create a loop. It is important to use a consistent URL format: whether it is HTTP or HTTPS, or the ‘www’ or root domain form, you must use the same one consistently across all layers of the configuration.
Why does the WordPress configuration cause a redirect loop?
WordPress can manage your website’s address and redirects in several places. If these settings differ from the rules specified by your hosting provider or a plugin, the system may send conflicting instructions to the browser. The ‘too many redirects’ error does not necessarily stem from a single incorrect setting: two rules operating independently of one another can also create a loop when combined.
The WordPress address and the website address
Once you’ve accessed the admin panel, you can check these two addresses on the Settings → General page. The ‘WordPress Address (URL)’ specifies where WordPress is installed, whilst the ‘Site Address (URL)’ determines the address at which the site is accessible to visitors. Ensure that the protocol and domain format are consistent across both fields.
For example, if the WordPress address is https://pelda.hu, but the website address is http://www.pelda.hu, the system is using a different protocol and www version. If another setting overwrites either of these, a loop may occur. First, make a note of the current values, and only change them once you have determined which version of the address the website should use.
If you are unable to log in to the administration panel, do not modify the addresses stored in the database without first checking them. An incorrect value may further impair accessibility. In such cases, please make a backup first, or request hosting-level assistance to check the settings.
Conflicts between HTTPS settings and extensions
The switch to HTTPS can be enforced by several layers: WordPress, a security or redirect management plugin, or the web server. If, for example, a plugin redirects to HTTPS whilst another rule redirects the request back to the original HTTP address, a redirect loop may occur. Check which settings handle HTTPS, and do not enable multiple redirects with the same function at the same time.
Exercise caution when testing plugins. Make a backup first, then disable just one plugin at a time – one that handles redirects or HTTPS enforcement – on a trial basis. Check the site after every change; this makes it easier to identify the faulty setting. Ensure that the change is reversible; do not delete any extensions or configuration files solely for the purpose of testing.
Further secure troubleshooting
If the URLs are consistent but the error persists, checking your WordPress logs may be the next step. A guide on troubleshooting WordPress by enabling WP_DEBUG mode can help you understand how to investigate PHP errors, but logging alone will not fix the redirect. Do not make the logs publicly accessible, as they may contain sensitive technical data. If you wish to review your WordPress operating environment, the WordPress hosting guide may provide further guidance.
If you are unable to carry out the investigation because the admin panel is unavailable, or if the error persists even after checking the plugins, please also review the server-side settings. A more detailed guide on WordPress and hosting may help you decide at which level of settings to continue your investigation.
Browser error or server-side redirection? Here’s how to tell the difference
You can narrow down the source of the ‘too many redirects’ error through targeted testing. First, check whether the issue only occurs in one browser and on one device, or whether it can be reproduced in other environments. Comparing the results across multiple browsers and devices will help you narrow down the location of the error. This will not automatically identify the faulty configuration, but it will show whether it is worth investigating the local browser settings or the website itself.
| Layer examined | Characteristic sign | What should you check? |
|---|---|---|
| Browser | The page loads in another browser or in a private window. | The website’s cookies and your browser’s local data. |
| WordPress | The error occurs in several browsers whilst the WordPress settings have been changed. | Website addresses, as well as plugins that handle redirects or HTTPS. |
| Server | The site cannot be accessed from various devices, and the server sends a redirect for every request. | The redirect rules applicable to the hosting account and the web server settings. |
| Domains and DNS | URLs with and without ‘www’ behave differently, or do not point to the same service. | The DNS records associated with the domain and the current hosting service. |
Quick checks in your browser
Open the same web address in a different browser or in an incognito window. If it loads there, clear the cookies for the website in question in your original browser, then try again. This test will not alter the website’s settings. If the page does not open in an incognito window either, or if you encounter the same error in multiple browsers, proceed to check WordPress and the server settings.
Domain, DNS and server-side discrepancies
Try opening the www and root domain addresses separately, then check whether both lead to the same intended version of the address. DNS records direct the domain to the correct destination, but redirection rules typically operate on the web server or the website itself. Do not modify the DNS simply because a record is recommended as a solution in the documentation for another platform.
Different services use different DNS settings and record values. Please check the records associated with your domain and hosting service against the relevant documentation. For example, do not copy Webflow’s A or CNAME records into the configuration of another service: platform-specific values may point to a different destination and cause further access errors. In a cPanel environment, the cPanel hosting information is directly relevant to this check when reviewing your hosting settings.
Fixing the ‘Too many redirects’ error in a safe order
Before making any changes, note down exactly when and at which address the error occurs. This way, after each modification, you can use the same test to check whether the behaviour has changed. Do not change several settings at once: if the error disappears or worsens, it will be easier to identify which change caused it.
- Reproduce the error. Open the affected page and make a note of the full URL, including the protocol, the ‘www’ version and the path. Check whether both the home page and a specific subpage are affected.
- Run a browser test. Try loading the page in a different browser or in an incognito window. If it works in one of these environments, check your browser’s local data first; do not modify the server configuration.
- Make a backup. Before making any changes to files, database settings or your WordPress configuration, make a backup of your files and database. Make a note of the original values so that you can restore them if necessary.
- Check your WordPress settings. Compare the protocol and domain variant used in the ‘WordPress Address’ and ‘Site Address’ fields. Then review any plugins that manage redirects or HTTPS enforcement. Change only one relevant setting at a time.
- Check the server-side rules. Compare the redirects in place on the hosting account with your WordPress settings. Only check the .htaccess file if the hosting account and web server in question use it. Do not insert generic rule code into an unfamiliar environment.
Targeted checks of WordPress settings
In the admin panel, you’ll find the ‘WordPress Address’ and ‘Site Address’ fields on the ‘Settings → General’ page. Use the same protocol and domain format for both. When testing plugins, make a backup, disable a single redirect management plugin, then repeat the same loading test. If the result remains the same, revert to the original settings before changing any other settings.
Server configuration and recovery
A server-side redirect may be correct in itself, but it may conflict with a rule in WordPress or a plugin. Check the destination URL set on the hosting account and the final URL version used in WordPress. Do not apply a specific DNS record or .htaccess rule without understanding how the web server and hosting account work.
If your website stops working properly after making a change, restore the backup of the original file or setting, then check the website again. For cPanel hosting, you can also review the settings associated with your hosting account via the cPanel control panel. If the error is related to server-side rules and the change cannot be safely reverted, please request support at the hosting level.
When should you seek hosting-level assistance for the ‘too many redirects’ error?
If the website displays the same error across multiple browsers and devices, the problem is unlikely to be caused solely by your browser’s local data. An investigation at the hosting level is also warranted if the request repeatedly encounters server-side redirects, the WordPress admin panel is inaccessible, or the error began after changes were made to the hosting settings. Do not attempt to add new rules at random, as this may make it even more difficult to identify the cause of the error.
Requesting assistance is more effective if the operating environment and any checks carried out to date are accurately documented. aWh’s knowledge base can also provide guidance on reviewing hosting-related settings before submitting a fault report.
What information should you include in your ticket?
Please describe the error in such a way that the technician investigating the issue can reproduce the problem. Provide the exact URL of the page in question, the error message displayed in the browser, and details of when and under what circumstances you encountered the problem. Please also indicate whether the issue occurs in the same way when using a different browser or device.
- Make a note of when the fault started and which pages are affected.
- List any WordPress settings, plugins, domain or server configurations that have been modified previously.
- Please describe what checks you carried out and whether the result changed after each test.
- Please do not include passwords, login details, secret keys or any other confidential access information in your bug report.
If you have restored a file or configuration from a backup, please mention this as well. A chronological record of changes helps to distinguish between redirects caused by WordPress’s operation and those resulting from the hosting provider’s rules. Accurate data reduces unnecessary troubleshooting and makes server-side troubleshooting more targeted.
How can the right hosting environment help?
Consistency in website and hosting settings makes it easier to identify errors. If the address used in WordPress, HTTPS handling and hosting redirects all follow the same definitive domain version, there is less chance of conflicting rules. When choosing a WordPress operating environment, aWh’s WordPress Hosting service provides pre-installed WordPress and the WordPress Toolkit Deluxe management tool.
aWh’s professional support team is available 24 hours a day. If the ‘too many redirects’ error occurs in multiple environments, or if your server settings need to be checked, please request hosting-level support. Discover aWh’s web hosting solutions and choose the environment that best suits your website’s operational needs.
Restore your website to reliable operation
Once the error has been resolved, document the changes you have made and keep a backup of the working configuration. This will make it easier to compare the new state with the previous one during any future updates or reconfigurations. If the ‘too many redirects’ error reoccurs, your notes will help you identify more quickly which change caused the problem.
For stable operation, it is also important that the settings for WordPress, the domain and the hosting are properly aligned. With over 10 years’ experience in the web hosting industry, aWh offers hosting solutions. When choosing the right environment, take into account your website’s operational requirements and the management options you need.
Take a look at aWh’s web hosting solutions and choose the option that best suits your website. The carefully documented settings and consistent hosting configuration provide a solid foundation for your website to serve its visitors reliably.
Frequently asked questions about the redirection error
What exactly does the ERR_TOO_MANY_REDIRECTS error mean?
This means that the browser is receiving repeated redirects and is unable to open the final address of the requested page. The ‘too many redirects’ error does not, in itself, reveal which setting is causing the problem. For example, a rule redirecting to HTTPS and another rule redirecting back to HTTP may be triggered one after the other. To identify the exact cause, check the settings of the browser, the website and the server separately.
Could browser cookies be causing the ‘too many redirects’ error?
Yes, due to a cookie stored for a website or your browser’s previous state, the error may only appear in your browser. Try opening the same page in an incognito window or in a different browser. If it loads correctly there, clear the cookies for that website and then try again. If the error occurs in multiple browsers and on different devices, it is more likely that the website’s settings need to be investigated further.
Why does the error also appear in the WordPress admin panel?
You may also be unable to access the admin panel if the WordPress installation URL and the website address provided to visitors use different protocols or domain variants. An HTTPS configuration or redirect plugin may also be causing the issue. If you are unable to log in for this reason, do not edit database values at random. First, back up your files and the database, then check whether any URL or plugin changes have been made previously.
Will switching to HTTPS resolve the ‘too many redirects’ error?
Not necessarily. HTTPS alone will not resolve the issue if the website, the hosting provider or an intermediary service is redirecting requests in different directions. For example, one setting may switch to HTTPS, whilst another redirects the browser back to HTTP. First, determine which layer is handling the redirection, and only modify the relevant setting. Do not disable encryption or website protection as a test.
Could a DNS error be causing the redirect loop?
DNS generally maps the domain name to its corresponding server; it does not carry out the HTTP redirection of the website itself. However, configuring it may still be important if, for example, the ‘www’ and non-‘www’ addresses lead to different servers, where different redirection rules apply. Before checking, please refer to the guide for your domain and hosting. Do not automatically apply A or CNAME records specified for other platforms.
What should I do if the error occurs in every browser?
If you experience the same issue in multiple browsers, make a note of the affected URL and the time the error was detected. Check whether the issue affects the homepage, the admin panel or just a subpage. Then review your most recent WordPress and hosting changes. Make a backup before making any changes to files or the database. If you do not have access to server-side redirects, please forward the recorded details to aWh’s support team.
Could editing the .htaccess file resolve the error?
Yes, if the loop is caused by a rule in this file, but .htaccess is not used in all hosting environments. Before editing, check the type of web server and create a backup of the original file. Do not copy and paste generic redirect code simply because it is listed as a solution on another website. Make changes one at a time, then check the homepage and the relevant URL.