• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Plesk suddenly redirects to hostname of server

King555

Regular Pleskian
On the 2nd of June I still was able to access my Plesk Onyx 17.5 via a domain name which is not the hostname of my server (without any redirects). Now I can't, I'm always redirected to the hostname of the server and my Plesk is not reachable under the IP behind this hostname (for security reasons).

Has an update been released which does this? I installed every update via the Linux command line.

I have installed the extension "Custom Plesk host" since April (when I installed Plesk) and it still contains the other domain name.

At this point I can only access Plesk by modifying my local hosts file under Windows.

Any ideas? Of course I could make Plesk accessible via the IP of the server's hostname, but I do not want this and this was not neccessary in any Plesk version before the 2nd of June. If an update did this, it was installed between the 3rd and the 17th of June.
 
Hi King555,

did you check the corresponding configuration files at "/etc/sw-cp-server/conf.d" and compaired them with previous suggestions here from the forum?

Example suggestion => #30
 
Thank you! I found out what's the problem. There are two files which were modified on the 14th of June, plesk.inc and ipv6_ports.inc. Seems like Plesk Onyx 17.5 MU #9 had been released on the 14th fixing this bug: https://talk.plesk.com/threads/sw-c...rect-disfunctional-in-plesk-onyx-17-5.342920/

First of all my ipv6_ports.inc was set to the default values. I had to enter the correct IPv6 IP and the port again. But the real problem is the line "error_page 497 https://$hostname:$server_port$request_uri;" in the file plesk.inc. I had to comment the line out to accecss my Plesk panel again. Is this line new? I guess so.

I think that the extension "Custom Plesk host" should modify this line...
 
Back
Top