Get The Most Affordable Hosting in the World!
Starting at just $1.87/month, Vercaa offers unbeatable pricing for world-class web hosting services.
Fast, reliable, and secure hosting to power your website without breaking the bank. Plus, enjoy a free CDN for faster loading times worldwide!
Get Started Now!Introduction
A redirect loop occurs when a website tells your browser to redirect to a page, which in turn tells your browser to redirect to another page, this happens over and over again until your browser stops redirecting and declares that a redirect loop has occurred. This varies from browser to browser, but is generally around 21 redirects.
Such a situation is typically caused by a misconfiguration of the website or the server.
Checking WHMCS Configuration
Ensure that the WHMCS System URL setting uses the correct URL for your website.
For help to check the system URL and update it, see Updating the System URL.
If the issue persists, continue to the next section.
Checking mod_rewrite Rules .htaccess
Redirect loops can be caused by .htaccess files which make use of an Apache mod called mod_rewrite. This is most commonly used for redirecting pages, creating human and search-engine-friendly URLs, and forcing pages to be loaded over a different protocol.
1. Reset the .htaccess file contents in your WHMCS directory.
For step-by-step instructions doing this, refer to this guide.
2. Navigate up the directory tree from the WHMCS directory and temporarily remove any other .htaccess files:
![Remove .htaccess files](https://media.screensteps.com/image_assets/assets/001/054/360/original/1aac1746-5ccb-486f-95f9-b0981bad5a58.png)
If the issue persists, continue to the next section.
Cloudflare SSL
If your website is protected by a Cloudflare SSL certificate, certain settings have been known to cause redirect loops in WHMCS. To resolve:
1. Login to your Cloudflare account
2. Click the Crypto heading
3. Change the SSL setting to Full or Full (Strict)
![](https://media.screensteps.com/image_assets/assets/001/054/363/original/a24d0525-62eb-400e-8e63-594de0d811d4.png)
The issue should now be resolved.