port 8443 re-direct

[wsani]

Hi,

When I go to http://server:8443 I get re-directed to https://localhost.localdomain:8443/

However, when I go to https://server:8443 it works. Where is the Plesk directive defined within Apache?

 

[breun]

The server running on port 8443 is httpsd (Plesk web interface) and separate from the httpd (apache) that serves your websites. What do you want to change?

 

[wsani]

Normally if you go to HTTP on port 8443, it'll re-direct you to HTTPS. I have several installs that will do this without any issues. However, in this instance, the HTTP is not re-directing to the hostname, instead it re-directs to https://localhost.localdomain:8443/ (exactly as you see it here).

I need to know which of the conf files retains the directives for this, so I can correct it.

 

[breun]

What is the output of the 'hostname' command on your server? Is the hostname of your machine set to 'localhost.localdomain'? What is the hostname set to in Plesk (Server > Server Preferences > Full hostname)?

 

[wsani]

The hostname is set to what its supposed to be on the OS and Plesk: L101 I'm pretty sure this is related to the web server.

 

[breun]

Your regular apache doesn't listen on port 8443, it's the internal Plesk webserver that's handling that.

 

[wsani]

okay the question now becomes, is there a way to correct the settings with the Plesk web server?

 

[breun]

I think it's the ServerName directive in /usr/local/psa/admin/conf/httpsd.conf. I believe Plesk sets this upon install, but maybe your hostname was still set to localhost.localdomain when you installed Plesk?

 

[wsani]

Thanks! That was exactly what I was looking for. The directive was using localhost.localdomain, which tells me that Plesk was setup using that hostname, then the hostname was modified.

 

[breun]

I believe Plesk should also update this file when changing the hostname in Plesk, but I haven't tested this.

 

[j0ney3]

Just tried it, it doesn't change the value for ServerName

 

[sergius]

Gentlemen,

Thank you for the report.
The issue actually exists. We will fix it as soon as possible.