• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Plesk-Site not accessible

Suprime

New Pleskian
Hello,

I am an absoulter Plesk noob, I know only the basic functions.

I took my page yesterday offline. (503 HTTP)

Now I wanted to take them online again this morning and when I now click on the domain, I get the error code "ERR_TOO_MANY_REDIRECTS"


Now I have asked my Hoster, they told me that I had something wrong on the web server and therefore the server tries to forward the domain constantly.

Here is an excerpt:

< HTTP/1.1 302 Moved Temporarily
< Server: nginx
< Date: Thu, 06 Oct 2016 05:16:14 GMT
< Content-Type: text/html; charset=utf-8 < Content-Length: 0 < Connection: keep-alive < Expires: Thu, 19 Nov 1981 08:52:00 GMT < Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 < Pragma: no-cache < Set-Cookie: WHMCS449RQwNPtUZa=ik0p95ais852llv3c5vqpnni95; path=/; HttpOnly < Location: http://mydomain.net < X-Powered-By: PleskLin < MS-Author-Via: DAV <
* Connection #0 to host mydomain.net left intact
* Issue another request to this URL: 'http://mydomain.net'
* Rebuilt URL to: http://mydomain.net/
* Found bundle for host dobster.net: 0x55b733ef8ce0 [can pipeline]
* Re-using existing connection! (#0) with host dobster.net
* Connected to dobster.net (88.198.X.X) port 80 (#0)
> GET / HTTP/1.1
> Host: mydomain.net
> User-Agent: curl/7.50.1
> Accept: /
>

This message comes again and again...

When I get the IP of the server in the Web calls I come to the default page of Plesk.
But I've seen in the web interface of Plesk, that the data is still there.

I guess it's due to Plesk, since I have actually done nothing else on the server.

I really hope someone can help me.
 
If you believe that Plesk is the culprit, try this command on the console:
/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain mydomain.net
(instead of mydomain.net type your domain name)

If the issue persists, it is a rewrite rule issue in your website. You have configured your hosting settings of the domain to choose either the non-www or the www-version, but you have not configured that the hosting settings accept both. Your website however insists on the www. version and the non-www. version of the URL in its configuration. So one version calls the other and vice versa which is causing a neverending redirect loop. You can easily solve this issue by changing your hosting settings to allow both URL types (with or without www; no default).
 
Back
Top