Resolved Cannot access Plesk because server redirects to it's hostname

[King555]

The problem in short:
I enter one of my IPs or the hostname belonging to this IP, followed by the Plesk port, and I get redirected to the "main" hostname of the server, which was set in Plesk. But at this moment that hostname is used by another server (my old server) and so I'm redirected to the other server and cannot access Plesk on the new server.

I don't know why Plesk reacts like this, because it did not on the old server. Here the problem more detailed:

I'm just configuring my new server with Plesk 11. My old server uses Plesk 10. On my old server / in Plesk 10 I have the following scenario:

- I have several IPs (10)
- Each IP is used for a different domain
- Each IP has it's domain as the reverse entry (configured outside of the server/Plesk)
- Each IP is set to "Dedicated" in Plesk
- I set Plesk to listen only on one of these IPs (and different port)
- Several domains are created in Plesk, but not a domain for my Plesk IP
- The server's name is one of the domains (required for mails not being recognized as spam)
- The hostname of the Plesk IP is one assigned by my provider (something like x-x-x-x.xyzservers.com)
- Entering the IP of Plesk redirects to the "Plesk hostname"
=> Plesk can be accessed by using x-x-x-x.xyzservers.com:myport

And under Plesk 11 (here comes the problem):

- Still several IPs (but less: 4)
- One IP should be used for Plesk, one for domain X, one for domain Y and the last one for the other domains
- Reverse entries are x-x-x-x.xyzservers.com for Plesk IP, domain X/Y for two other IPs and the main domain for the last IP
- Plesk IP and the two single domain IPs are configured as dedicated, the last one as shared
- At this point I did not configure any domains in Plesk
- Server's name is the same as my old server (the main domain)
=> Entering any IP with the Plesk port redirects to the servers hostname, e.g. my main domain, which is still on the old server.
=> Result: I cannot access Plesk!

Of course I could just change the hostname of the server via SSH (just have to find out how to do this), but why does Plesk react in another way now? Or is the problem that I cannot change Plesk to listen on only one IP?

I hope my problem can be understood. If not, please ask.

Thanks for any help!

 

[Sergey L]

The redirect you describe might be caused by Single Sign On service used in Plesk for some integrations. It wasn't enabled in default configuration of Plesk 11 (unless you chose to install Customer and Business Manager). If that would be the reason, you can follow this KB http://kb.parallels.com/en/9327 How to remove Customer and Business Manager (CBM, former Plesk Billing) from Parallels Plesk Panel and disable SSO.

 

[King555]

Thanks for your reply. I did not install that package and I just checked it via SSH (/usr/local/psa/admin/bin/autoinstaller), it's not installed.

And I ran the command "/opt/psa/bin/sso --disable" (and restarted the Plesk web server). Does not help, I'm still redirected, no matter whether I use the IP or the hostname of this IP.

 

[King555]

I had an idea and I edited my Windows hosts file (/system32/drivers/etc/) and added the following:

x.x.x.x domain.com

(x.x.x.x is the IP of the new server and domain.com the hostname of the new server, which is also the main domain and hostname of the old server).

This works, now I can enter Plesk. What's strange to me: I can still access my domain on the old server.

And I found something out: It's a Plesk only problem. When I enter the hostname of the IP I want to use for Plesk on the new server, I see a Plesk default page (i.e. the webserver does not redirect). But when I use the Plesk port I'm redirected. Bug?

 

[King555]

After my server exchange is finished completely, this problem is solved. The old server is gone now and all domains point to the new server. Now I can enter Plesk normally.

I don't know what the exact problem was and at which point it was solved. But it is solved.

 

[scotty12]

Just run into the same problem using Plesk 12 Pro. I only get redirected, if just enter [myipadress]:8443 into the adressbar of my browser. Now he tries to connect to http://[myipadress]:8443 and gets redirected to https://[myhostname]:8443. But when I enter https://[myipadress]:8443 into the adressbar, I don't get redirected and can login to the machine with that ip.

 

[Sergey L]

Your "problem" is different and isn't a problem at all in fact. The system tries to redirect you to the right entrypoint which is https://...:8443
Adding http:// at first step isn't a redirect, it is your browser completing address line to the proper format. Then the server redirects you to secure entry point at https://, since http:// isn't a correct point

When you type https:// you get straight into secure entry point and no redirect happens (whatever you put in between of https:// and :8443)

 

[Sergey_Ugdyzhekov]

In short, you can change this behavior if it's not applicable for you. There is article about how it works in Plesk: http://devblog.plesk.com/2013/12/about-plesk-url-or-telling-customers-the-right-address-to-go-to/