How to Fix CloudPanel Nginx Redirect Loop in WordPress

If you have just migrated a site to CloudPanel or hooked up Cloudflare, hitting an infinite 301 redirect error is a common headache. To fix cloudpanel nginx redirect loop issues, you need to understand how Nginx, PHP-FPM, and your SSL termination layer communicate about the security status of incoming requests.

When WordPress receives an insecure HTTP request, it automatically redirects the user to the HTTPS version of the URL. However, if your site is behind a reverse proxy (like Cloudflare, AWS ALB, or KeyCDN) that communicates with your CloudPanel server over HTTP, WordPress fails to recognize that the original connection was secure. It redirects the visitor again, creating an infinite loop that crashes the browser with a “Too Many Redirects” error.

Why the CloudPanel Nginx Redirect Loop Occurs

CloudPanel uses a highly optimized Nginx stack. By default, Nginx expects SSL handshakes to happen directly on the server. When you introduce a proxy, the architecture changes. The client connects to Cloudflare via HTTPS, but Cloudflare connects to your CloudPanel origin server over HTTP (port 80).

Because CloudPanel receives the request on port 80, Nginx passes standard non-secure FastCGI parameters to PHP. WordPress looks at the PHP global variables, concludes the site is being accessed insecurely, and issues a 301 redirect. The proxy receives this redirect, passes it back to the client, and the loop begins. To fix this, we must configure WordPress to trust proxy headers and ensure Nginx is passing the correct FastCGI parameters.

Step 1: Update wp-config.php to Recognize Reverse Proxies

The first and most reliable step is to tell WordPress to look for the HTTP_X_FORWARDED_PROTO header. This header is sent by Cloudflare and other load balancers to indicate whether the original user connected via HTTP or HTTPS.

Open your wp-config.php file in the CloudPanel file manager or via SSH, and add the following lines at the very top of the file, right after the opening PHP tag.

wp-config.php
<?php
/** Detect SSL behind Cloudflare or reverse proxies */
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') {
    $_SERVER['HTTPS'] = 'on';
}

if (isset($_SERVER['HTTP_X_FORWARDED_SSL']) && $_SERVER['HTTP_X_FORWARDED_SSL'] === 'on') {
    $_SERVER['HTTPS'] = 'on';
}

This snippet intercepts the incoming request. If the proxy confirms the connection was secure by setting the X-Forwarded-Proto header to https, we manually force the PHP HTTPS global variable to ‘on’. WordPress will now correctly recognize the secure connection and stop issuing 301 redirects.

Step 2: Adjust Nginx Vhost Configuration in CloudPanel

If editing wp-config.php alone does not fix cloudpanel nginx redirect loop problems, the issue likely resides in how Nginx passes parameters to the FastCGI process. We need to ensure Nginx evaluates the proxy headers and sets the FastCGI parameter correctly.

Log in to your CloudPanel dashboard, go to your site settings, click on the “Vhost” tab, and inspect your configuration. Look for the block handling PHP files (usually containing fastcgi_pass). You need to ensure the fastcgi_param HTTPS variable is dynamic.

nginx.conf
# Ensure CloudPanel map block is present at the top of Nginx config or handled via vhost
map $http_x_forwarded_proto $fe_https {
    default $https;
    https 'on';
}

# Inside your server block location ~ \.php$ rule:
location ~ \.php$ {
    try_files $uri =404;
    fastcgi_split_path_info ^(.+\.php)(/.+)$;
    fastcgi_pass unix:/run/php/php8.2-fpm.sock;
    fastcgi_index index.php;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    fastcgi_param HTTPS $fe_https;
}

The map block at the top checks the value of $http_x_forwarded_proto. If it is set to “https”, it sets our custom $fe_https variable to “on”. This variable is then passed to FastCGI. This keeps your site secure and prevents Nginx from serving false security signals to WordPress.

Step 3: Fix Cloudflare SSL/TLS Settings

If you are using Cloudflare, the “Flexible” SSL setting is a notorious culprit for this exact issue. Flexible mode encrypts traffic between the browser and Cloudflare, but sends unencrypted HTTP traffic to CloudPanel. Because of this, Nginx thinks the request is insecure and tries to force SSL, while Cloudflare redirects HTTP traffic back to HTTPS.

To resolve this loop immediately:

1. Log in to your Cloudflare Dashboard.
2. Select your domain and navigate to the SSL/TLS tab.
3. Change the encryption mode from “Flexible” to “Full” or “Full (Strict)”.

Note: To use “Full (Strict)”, you must have a valid SSL certificate installed on your CloudPanel server. CloudPanel makes this easy with its built-in Let’s Encrypt integration. Always use Full (Strict) in production environments to ensure end-to-end encryption.

Step 4: Verify the Fix with Curl

Once you have applied these configurations, clear your local browser cache and verify the redirect headers using the command line. This avoids cached redirects in your browser from giving you false results.

terminal
curl -IL https://yourdomain.com

Analyze the output. You should see a single HTTP/2 200 OK response. If you see multiple HTTP/2 301 responses repeating the same target URL, your redirect loop is still active. Double-check that your CloudPanel Nginx Vhost has been reloaded after editing by running ‘ngx_reload’ or restarting the Nginx service in the CloudPanel UI.