• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Problems after Panel Upgrade - Plesk runs at Port 8443 not 443 like before

davemoondog

davemoondog

Basic Pleskian
4 hours ago the Plesk panel updated itself

Code: 
Plesk Installer 3.38.0 (revision 3bb60484a443) started at (timezone CET) Thu Sep 23 06:17:03 2021
Command line arguments: /var/cache/parallels_installer/parallels_installer_Ubuntu_18.04_x86_64_3.38.0 upgrade plesk 18.0.38

It seems the Plesk backend is not accessible on Port 443 like before, but under Port 8443 that is blocked by our firewall. We had to update our firewall settings, in order to access the backend again.

  • Have others experienced similar problems?
  • What is the reason for Plesk to change the port?
  • Now we have to add :8443 to the URL, otherwise the site is stated to be insecure. Why is the site not secure without the addition of the port to the URL?
  • How can we reverse the changes by Plesk?
cheers and thanks for the help
 
You must log in or register to reply here.

Similar threads

D
Question Service Unavailable port 8443 Plesk Not Working
Replies
1
Views
7K
Kaspar@Plesk
Kaspar@Plesk
T
Question Using an external firewall to block Plesk ports
Replies
3
Views
2K
thinkjarvis
T
K
Issue Custom port for Plesk seems to be not reachable anymore by external services after latest upgrade
Replies
2
Views
1K
King555
K
randypetersen
Question After upgrade PHP-FPM has high cpu usage.
Replies
6
Views
11K
Peter Debik
P
C
Issue Can't access Updates and Upgrades. Port 8447 appears to be closed. Can't open.
Replies
6
Views
5K
KendalSmithy
K
Back
Top