Can't access port 8443

[jaynXX]

after a full install plesk 8.6 on cent 5.2 .went to log on page https://100.000.00:8443


Can't access port 8443 Server not found page error

 

[breun]

100.000.00 doesn't look like a valid hostname or IP address.

 

[jaynXX]

if its ok i rather not post my IP. i dont have control of the admin. i do have the right and correct IP.

 

[breun]

What does service psa status say? If it's not running, try service psa start.

Are you sure there is no firewall blocking access to port 8443?

 

[jaynXX]

Please click one of the Quick Reply icons in the posts above to activate Quick Reply.

 

[jaynXX]

[root@p ~]# service psa start
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Starting Plesk... done
Starting drwebd service... failed


still no admin page

 

[leslierad]

Changing default port Plesk 8.6 from 8443

My brother has the same issue as mentioned above when trying to log in via port 8443 the default plesk port.

Yet I am able to login, he reinstalled windows as he couldn't find anything blocking that port, it appears that the ISP has blocked it, I am now trying to find detailed instructions to change the port for plesk for ver 8.6 as I have found differing versions online to fix the issue but nothing official.

Please post detailed instructions to change the default port from 8443 in plesk 8.6

Thanks, that may solve your issue too, jaynXX

 

[breun]

Your ISP is blocking port 8443? That's one strange ISP. I'd ask them why.

The port is defined in /usr/local/psa/admin/conf/httpsd.conf (four instances of the number 8443 in there). Also see http://kb.odin.com/en/138

 

[leslierad]

Yes either his ISP or router is blocking the port, the ISP deny any port blocking so who knows what the issue is, anyway thanks for confirming the KB article, I had already seen that, just wanted to be sure, the file you mentioned httpsd.conf has the following remarks in the header:

# DO NOT EDIT THIS FILE!
# The contents of this file will be overwritten next time you upgrade Plesk
# or apply a patch to it, so any changes you make to this file will be lost.
#
# If you need custom changes, you should modify the
# file /usr/local/psa/admin/conf/httpsd.custom.include

So I guess I will need to update httpsd.custom.include too so that the next update to plesk changes are not lost

Any suggestions to an allowed port I was going for 23 yet in the KB reference "Please note that none of the ports (21, 22, 23, 25, 53, 80, 110, 443, etc...) used for the standard web hosting services (Apache, POP, SMTP, mySQL, proFTPd, BIND) can be used." other articles I read suggested changing to port 23 (Telnet) as that port should be unblocked, now I'm in 2 minds.

 

[leslierad]

I tried changing the above to port 23 - no luck. It even worsened the situation as I could no longer connect - lol
ended up connecting via http:// & :8880