• 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.

Port conflicts with plesk

V

vietlongle

Guest
Hi,

After setting up a domain and dns in plesk, i couldn't resolve the domain name in a browser, and eventually found out that it was because my Fedora OS was blocking port 53 by default.

After updating the iptables file to open up port 53, the plesk server running on port 8443 no longer responds (the browser says 'connected', but it just hangs there).

In addition to this, i can no longer ssh via putty to the server as whilst it lets me enter a username, it hangs after i put in a password.

Can anyone please advise me what the problem may be, and what the appropriate port filtering settings in the iptables file should be?

thanks!
 
Back
Top