Today, I wrote a small tutorial about how to run Plesk on port 443 using mod_proxy.
—————————————————
This howto describes the configuration of your server to let your users login to plesk using standard ports 80 (http) and 443 (https). This is especially helpful, if you are behind any kind of firewall or proxy, which prohibits access to plesk’s standard port 8443. This solution uses mod_proxy to create an internal forward from ports 80/443 to port 8443.
Please notice, that you will not have access to the Virtuozzo Panel in Plesk when using this solution. But as access to Plesk and(!) Virtuozzo Panel is still available on Port 8443, this should not be problem for your clients.
I created this howto on a Debian Linux system. Therefore you will have to replace some of the commands with commands of the Linux distribution, which you are using. Basically, the configuration should work on any Linux system.
My test system: VPS, Debian 3.1, Plesk 8
(1) install mod_proxy_html
apt-get install libapache2-mod-proxy-html
(2) activate mod_proxy_html in apache configuration
a2enmod proxy_html
(3) create subdomain with ssl support through Plesk (example: plesk.example.com)
(4) create a file called vhost.conf in /var/www/vhosts//subdomains/plesk/conf/ and insert the following options:
ProxyPass / https://localhost:8443/
<Location />
ProxyPassReverse /
</Location>
SSLProxyEngine On
<Proxy *>
Order deny,allow
Deny from all
Allow from all
</Proxy>
(5) let Plesk reconfigure your domain (replace example.com with your domain)
/usr/local/psa/admin/sbin/websrvmng –reconfigure-vhost –vhost-name=example.com
(6) restart Apache
/etc/init.d/apache2 restart
(7) access Plesk using https://plesk.example.com or http://plesk.example.com
(8) Send me an eCard, email or comment this blog entry directly to give feedback on this tutorial. 
—————————————————
Wer keine eigene SSL-Site nutzt oder eh noch eine SSL-freie IP-Adresse hat, kann einfach in /usr/local/psa/admin/conf/httpsd.conf (Achtung: liegt manchmal auch unter /srv/…) alle Vorkommen von 8443 in 443 umzuwandeln.
Danach Plesk mit “/etc/init.d/psa restart” neustarten.
Schon hat man das selbe Ergebnis.
huschi.
Hi huschi,
das stimmt. Aber würde mich wundern wenn jemand bei einem VPS kein SSL nutzen würde…
Hi Huschi,
nur machst du eine kleines Update in Plesk musst du es wieder neu eintragen und das ist also nicht auf dauer….
Well huge thanks to you ! I’ve searched through a way to do this correctly for a whole month, without finding anything successful. This post deserves to be made publicly available so that everyone who needs to pass through a company firewall can do it with ease !
Thanks again
ich bekomme beim betreten von plesk.domain.com diese fehlermeldung:
”
Forbidden
You don’t have permission to access / on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
”
was könnte der grund für dies sein?
can you tell me how to block https://www.domain.tld:8443/ for each domain on Plesk, can I use vhost.conf
Because Google is indexing my plesk login pages for many domains and when is indexed it won’t index any other pages of the site. The worse I get Google visitors hitting the PLESK login page instead of the main index page every day.
So i thought would be good to block the plesk login for each domain, as I only login to the main server rather than the domain. This may also block Google from indexing it.