Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
So, we have decided to switch back to cPanel. It was nice experience with Plesk panel, but we are not willing to pay for each simple "add-ons", tools etc. which are normaly free and included in cPanel. Also such things/add-ons like 'Juggernaut Security and Firewall' (what is simply a 'clone' of...
Seems to be nice hot here... BTW cPanel license with unlimited accounts on it (as before) costs $14.95 from a reliable reseller. We used cpanel for years, now we tried Plesk, but with such things what happened and their "mind" we will probably switch back to cPanel.
Sorry, but I don't understand what do you mean. If I have a VPS with 2TB HDD, 32BG RAM, 16 vCPUs then I will not be able to create e.g. 100 Plesk accounts/domains/subscriptions, but on a dedicated server e.g. with 500GB HDD, 16GB RAM and 8 vCPUs I would? Really don't understand the point. Could...
Ok, the problem solved. The solution is:
after changing the port in 'sshd_config' and '/etc/services' you have to restart the ssh service from the command line or on what's ever way. The reboot from Plesk admin panel, ssh console or from the VPS panel doesn't restart the ssh service.
Or won't...
I use the Juggernaut Security and Firewall and both ssh ports have been allowed there. But still no ssh access.
Now we change back the ssh port to 22 in 'ssh_config' and 'sshd_config' and we can log in again with port 22. Notice that before we tried many things: the firewall has been disabled...
After changing the port in 'sshd_config' now no ssh access is working:
Network error: Connection refused
No port 22 nor xxx the changed one... Ok, what is the next step to get this fixed for ever?
This has been changed as well in '/etc/services' to:
ssh 988/tcp # The Secure Shell (SSH) Protocol
ssh 988/udp # The Secure Shell (SSH) Protocol
But after reboot the ssh port is still 22:
# semanage port -l | grep ssh...
Hi, it seems it was a false alarm. The ssh port 988 still doesn't work.
1. this has been added to '/etc/services':
ssh 988/tcp # The Secure Shell (SSH) Protocol
ssh 988/udp
2. this is in the 'etc/ssh/ssh_config':
# Site-wide defaults for...