Facebook
Twitter-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Resolved 502 Bad Gateway
- Thread starter Bammer013
- Start date
The cause is probably a corrupted /opt/psa/admin/conf/httpsd.pem file. Plesk create automatic backups of that file, so you should be able to restore it from such a backup:
should result in something like
-r-------- 1 root root 1922 Jan 27 12:59 /opt/psa/admin/conf/httpsd.pem
-r-------- 1 root root 6525 Jan 27 12:55 /opt/psa/admin/conf/httpsd.pem.sav
Then you can
Afterwards, login to Plesk an create a new certificate as described in https://support.plesk.com/hc/en-us/articles/12377713798039 .
ls -l /opt/psa/admin/conf/httpsd.pem*should result in something like
-r-------- 1 root root 1922 Jan 27 12:59 /opt/psa/admin/conf/httpsd.pem
-r-------- 1 root root 6525 Jan 27 12:55 /opt/psa/admin/conf/httpsd.pem.sav
Then you can
mv /opt/psa/admin/conf/httpsd.pem /opt/psa/admin/conf/httpsd.pem_not_workingcp -p /opt/psa/admin/conf/httpsd.pem.sav /opt/psa/admin/conf/httpsd.pemAfterwards, login to Plesk an create a new certificate as described in https://support.plesk.com/hc/en-us/articles/12377713798039 .
