Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: 1 [2]
16
CentOS Configuration / Re: ERR_TOO_MANY_REDIRECTS
« on: February 24, 2020, 11:08:30 PM »clear the varnish cache and restart varnish for the checks.
Yes, I did that, but it's only a temporary fix.
The problem comes back and I cannot be there each time to manually restart.
Excluding the home page could be a solution, but how do I do that?
17
CentOS Configuration / Re: ERR_TOO_MANY_REDIRECTS
« on: February 24, 2020, 03:51:29 PM »
I have been trying to trace down the same problem. I managed to identify the exact problem, and I am putting it here for requesting a solution.
The ERR_TOO_MANY_REDIRECTS appears for the wordpress homepage only and it goes away and then comes back on my site, Thinkbalm. This periodical bahavior gave the clue that it is a cache-related problem.
Status 301 Moved Permanently
Server nginx/1.16.1
Date Mon, 24 Feb 2020 15:46:29 GMT
Content-Type text/html; charset=iso-8859-1
Content-Length 230
Connection keep-alive
Keep-Alive timeout=60
Location https://thinkbalm.com/
X-Varnish 98379 131369
Age 13
Via 1.1 varnish (Varnish/5.2)
X-Cache HIT from Backend
I am using Nginx > Varnish > Apache, php-fpm. Setting the domain's configuration to Nginx > Apache, thereby taking out Varnish solves the problem, but then you lose your Varnish cache. Therefore I did a lot of searching and the problem seems to be the following:
Varnish and SSL - WordPress Behind an HTTPS Terminating Proxy
Varnish is a reverse caching proxy server that speeds up the performance of your website. It is commonly used in conjunction with WordPress.
Unfortunately, Varnish does not support SSL. So we need to terminate the SSL connection and speak plain HTTP with Varnish and your WordPress site.
Not only does Varnish not support SSL, it is also unaware of the SSL termination and just uses the hostname and the URL of the request as an identifier.
We trigger a problem: forcing HTTPS redirects on an application that is not aware what the initial request protocol, can cause ERR_TOO_MANY_REDIRECTS errors in your browser.
This happens when the HTTP version of a page is stored in cache. The output is nothing more than a 301 redirect to the HTTPS version. But because Varnish and WordPress are unaware of SSL termination, you’ll end up in a redirection loop until the browser throws this error.
How can we solve this?
I tried adding this to the wp-config file:
if($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https'){
$_SERVER['HTTPS'] = 'on';
$_SERVER['SERVER_PORT'] = 443;
}
I also tried to add this to .htaccess:
SetEnvIf X-Forwarded-Proto "https" HTTPS=on
Header append Vary: X-Forwarded-Proto
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteCond %{HTTP:X-Forwarded-Proto} !https [NC]
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</IfModule>
None of these resolved the situation.
Any ideas?
The ERR_TOO_MANY_REDIRECTS appears for the wordpress homepage only and it goes away and then comes back on my site, Thinkbalm. This periodical bahavior gave the clue that it is a cache-related problem.
Status 301 Moved Permanently
Server nginx/1.16.1
Date Mon, 24 Feb 2020 15:46:29 GMT
Content-Type text/html; charset=iso-8859-1
Content-Length 230
Connection keep-alive
Keep-Alive timeout=60
Location https://thinkbalm.com/
X-Varnish 98379 131369
Age 13
Via 1.1 varnish (Varnish/5.2)
X-Cache HIT from Backend
I am using Nginx > Varnish > Apache, php-fpm. Setting the domain's configuration to Nginx > Apache, thereby taking out Varnish solves the problem, but then you lose your Varnish cache. Therefore I did a lot of searching and the problem seems to be the following:
Varnish and SSL - WordPress Behind an HTTPS Terminating Proxy
Varnish is a reverse caching proxy server that speeds up the performance of your website. It is commonly used in conjunction with WordPress.
Unfortunately, Varnish does not support SSL. So we need to terminate the SSL connection and speak plain HTTP with Varnish and your WordPress site.
Not only does Varnish not support SSL, it is also unaware of the SSL termination and just uses the hostname and the URL of the request as an identifier.
We trigger a problem: forcing HTTPS redirects on an application that is not aware what the initial request protocol, can cause ERR_TOO_MANY_REDIRECTS errors in your browser.
This happens when the HTTP version of a page is stored in cache. The output is nothing more than a 301 redirect to the HTTPS version. But because Varnish and WordPress are unaware of SSL termination, you’ll end up in a redirection loop until the browser throws this error.
How can we solve this?
I tried adding this to the wp-config file:
if($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https'){
$_SERVER['HTTPS'] = 'on';
$_SERVER['SERVER_PORT'] = 443;
}
I also tried to add this to .htaccess:
SetEnvIf X-Forwarded-Proto "https" HTTPS=on
Header append Vary: X-Forwarded-Proto
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteCond %{HTTP:X-Forwarded-Proto} !https [NC]
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</IfModule>
None of these resolved the situation.
Any ideas?
18
PHP / Re: PHP Version Switcher
« on: December 01, 2019, 06:44:27 AM »
Hello,
How do I install PHP 7.4 with the PHP Switcher?
It doesn't work for that version.
How do I install PHP 7.4 with the PHP Switcher?
It doesn't work for that version.
Pages: 1 [2]
