> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.xynta.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# What does “Too many redirects” mean and how can I fix it?

The **"Too many redirects"** error occurs when a website enters an endless redirection loop, repeatedly redirecting the browser between different URLs without reaching a destination.

* [Possible causes](#3-possible-causes)
* [Possible solution: Disable "Force SSL with HTTPS Redirect"](#3-possible-solution-disable-force-ssl-with-https-redirect)
---

### Possible causes

* **Misconfigured website settings:**
  Incorrect URLs (e.g., in WordPress) can trigger redirect loops.

* **Problems with the .htaccess file:**
  Incorrect or conflicting rules can cause unintended redirects.  
  ➔ [Test your .htaccess file](https://htaccess.madewithlove.com/)

* **SSL/TLS configuration issues:**
  Forcing HTTPS without a valid SSL certificate can lead to too many redirects.

* **Incorrect redirect rules in server configuration:**
  Faulty or duplicate redirect rules can create a redirection loop.

* **Plugin or theme conflicts (in CMS systems like WordPress):**
  Conflicts between plugins or themes can cause faulty redirects.
---

### Possible solution: Disable "Force SSL with HTTPS Redirect"

Sometimes, the **"Force SSL with HTTPS Redirect"** setting on Web and Reseller Hosting packages can cause this error.

Follow these steps to disable it:

1. Log in at [https://voorbeeld.cc:2222](https://voorbeeld.cc:2222) (or use [Single Sign-On (SSO)](/en/article/logging-in-to-hosting-package-via-single-sign-on-sso-1biycbb/)).
2. Under **Account Manager**, click **Domain Setup**.
3. Select the domain where you want to disable the setting.
4. Uncheck the option **Force SSL with https redirect**.
5. Click **Save**.
---

🔍 Afterwards, check if the error is resolved.  
If so, there was likely a conflict with a rule in your .htaccess file or site configuration.

||| 🔄 Remember to replace **voorbeeld.cc** with your own domain name.