You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix: $scheme variable now correctly uses HTTPS connection status
- Added is_https parameter to handle_proxy function
- Added is_https parameter to expand_proxy_header_value function
- $scheme now correctly returns 'https' when client connects via SSL
- Fixes WordPress login cookie issues when behind reverse proxy
1.**Clear your browser cookies** for the WordPress site after making configuration changes
316
+
317
+
2.**Check that your site URL is correct** in WordPress Settings → General (Site URL and WordPress URL should both use `https://`)
318
+
319
+
3.**Verify headers are being passed** by checking your server logs or using browser developer tools to inspect request/response headers
320
+
321
+
4.**If using load balancing with multiple backends**, ensure you're using `ip_hash` for sticky sessions:
322
+
```nginx
323
+
upstream backend_servers {
324
+
ip_hash;
325
+
server 10.0.10.101;
326
+
server 10.0.10.102;
327
+
}
328
+
```
329
+
330
+
5.**Check for redirect loops** - if WordPress and your proxy disagree about HTTP vs HTTPS, you'll get infinite redirects. The `X-Forwarded-Proto` header and `wp-config.php` settings above should fix this.
0 commit comments