Comments on: Running Plesk on port 443 http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/ Christian's Blog Sat, 29 May 2010 04:34:26 +0000 hourly 1 http://wordpress.com/ By: Pablo http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/#comment-2871 Pablo Wed, 21 Apr 2010 18:01:22 +0000 http://blog.thebartels.de/index.php/2006/05/16/running-plesk-on-port-443/#comment-2871 This worked fine for me with Plesk 8 but with Plesk 9.5 is not working, I login and then get redirected to the :8443 url. any ideas? thanks! This worked fine for me with Plesk 8 but with Plesk 9.5 is not working, I login and then get redirected to the :8443 url. any ideas?

thanks!

]]> By: Plesk control panel access as a virtual domain- Enjoy! http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/#comment-2802 Plesk control panel access as a virtual domain- Enjoy! Thu, 24 Dec 2009 19:08:20 +0000 http://blog.thebartels.de/index.php/2006/05/16/running-plesk-on-port-443/#comment-2802 [...] and reading many various proxy solutions and approaches, I discovered a posting on theBartels.de, Running Plesk on Port 443, that covered my requirements and almost worked for me.  I recommend reading the excellent [...] [...] and reading many various proxy solutions and approaches, I discovered a posting on theBartels.de, Running Plesk on Port 443, that covered my requirements and almost worked for me.  I recommend reading the excellent [...]

]]> By: Alex http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/#comment-1753 Alex Mon, 16 Jun 2008 23:46:07 +0000 http://blog.thebartels.de/index.php/2006/05/16/running-plesk-on-port-443/#comment-1753 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. 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.

]]> By: forquato http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/#comment-1751 forquato Wed, 05 Dec 2007 16:49:55 +0000 http://blog.thebartels.de/index.php/2006/05/16/running-plesk-on-port-443/#comment-1751 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? 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?

]]> By: Dhaya http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/#comment-1752 Dhaya Wed, 05 Dec 2007 00:58:29 +0000 http://blog.thebartels.de/index.php/2006/05/16/running-plesk-on-port-443/#comment-1752 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 ;) 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 ;)

]]> By: blog.theBartels.de » Blog Archive » Howto: AJAX-based SSH client for your Debian+Plesk Setup (AjaxTerm) http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/#comment-1750 blog.theBartels.de » Blog Archive » Howto: AJAX-based SSH client for your Debian+Plesk Setup (AjaxTerm) Mon, 11 Dec 2006 22:46:54 +0000 http://blog.thebartels.de/index.php/2006/05/16/running-plesk-on-port-443/#comment-1750 [...] 5. Make the init script executable and start AjaxTerm # chmod a+x /etc/init.d/ajaxterm # /etc/init.d/ajaxterm start Starting ajaxterm on port 8022 AjaxTerm at http://localhost:8022/ pid: 7580 AjaxTerm is now successfully running (it started ssh session on localhost with user nobody) but is only listening on localhost:8022. Therefore we will use the Apache proxy module to access AjaxTerm using a subdomain. (As we did in the Plesk on Port 443 Howto) [...] [...] 5. Make the init script executable and start AjaxTerm # chmod a+x /etc/init.d/ajaxterm # /etc/init.d/ajaxterm start Starting ajaxterm on port 8022 AjaxTerm at http://localhost:8022/ pid: 7580 AjaxTerm is now successfully running (it started ssh session on localhost with user nobody) but is only listening on localhost:8022. Therefore we will use the Apache proxy module to access AjaxTerm using a subdomain. (As we did in the Plesk on Port 443 Howto) [...]

]]> By: Simon http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/#comment-1749 Simon Mon, 05 Jun 2006 13:58:05 +0000 http://blog.thebartels.de/index.php/2006/05/16/running-plesk-on-port-443/#comment-1749 Hi Huschi, nur machst du eine kleines Update in Plesk musst du es wieder neu eintragen und das ist also nicht auf dauer.... Hi Huschi,
nur machst du eine kleines Update in Plesk musst du es wieder neu eintragen und das ist also nicht auf dauer….

]]> By: CB http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/#comment-1748 CB Tue, 16 May 2006 19:01:10 +0000 http://blog.thebartels.de/index.php/2006/05/16/running-plesk-on-port-443/#comment-1748 Hi huschi, das stimmt. Aber würde mich wundern wenn jemand bei einem VPS kein SSL nutzen würde... Hi huschi,

das stimmt. Aber würde mich wundern wenn jemand bei einem VPS kein SSL nutzen würde…

]]> By: huschi http://blog.thebartels.de/2006/05/16/running-plesk-on-port-443/#comment-1747 huschi Tue, 16 May 2006 18:35:19 +0000 http://blog.thebartels.de/index.php/2006/05/16/running-plesk-on-port-443/#comment-1747 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. 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.

]]>