• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Cannot open "Updates and Upgrades" (Conn Refused)

Winnstorm

Basic Pleskian
Hello,

Im facing a problem trying to get to Updates and Upgrades page of plesk. When I get redirected to https://..:8447 I get a Connection Refused error con Chrome.
As far I checked I've both ports 8443 and 8447 in iptables:

# iptables -nL | grep 8443
f2b-plesk-login tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 8880,8443
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8443
# iptables -nL | grep 8447
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8447
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8447

Also in PLESK Firewall the Installer is enabled too.

Im not sure how to fix this issue.

Hope somebody can guide me to a fix.

Thanks!
Best regards
 
@Winnstorm

Just try to change a firewall rule in the Plesk Firewall extension first.

It can be the case that the firewall extension is not setting firewall rules properly : a small change is often sufficient to allow proper functioning of the Plesk firewall.

As a second step, being a step that you have to execute : check your own IP and check whether your IP is banned by Fail2Ban.

If your IP is banned, just make it a "trusted IP" - and everything should work fine.

Hope the above helps a bit - keep us posted!

Regards.......
 
Back
Top