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.
Hi,
Installed 18.0.55 at many servers, everything went ok.
At one server there is strange behaviour though
Installed successfully (and still working fine) but at home
i see this
Plesk Obsidian
Version 18.0.55, last updated on Aug 27, 2023 02:58 AM
while it was updated at September2
And not...
And here is the most funny screenshot, at only one machine, prooves the mess with psa-firewall and plesk-firewall names of service
psa-firewall service not found but active!
plesk-firewall service loaded but inactive!
firewall works ok though, Peter if any idea please share
Here it is:
Here is the normal at 10 servers as plesk installed by provider and i just enabled the extension, all work pretty well, iptables.service is not installed by default in Almalinux
Thanks for reply
I have about 10 servers at same provider with almalunux 8 / plesk, iptables.service is by default disabled along with firewalld (from the provider's plesk installation)
and plesk firewall works very fine without doing anything except activating firewall from plesk.
At other...
FirewallD as Peter mentioned should be correctly disabled (or masked)
plesk-firewall service is correctly enabled
As for iptables, did not find any documentation on this, but as i tried myself
realized that iptables and iptables.service at least at Almalinux are different things.
Almalinux 8...
Hi Peter thanks for coming back
Right when disabling firewallD locked out, obviously it deletes the 3 default entries at iptables including ssh
It seems that depends on how plesk installed by the provider, at main vps/dedicated provider i use
never have proble, just activating plesk firewall and...
Hi Tim
At that almalinux/plesk machine if i remember well i did this:
iptables -S had the open ports (this is tables not the service, obviously the ports added by firewalld)
Then before disabling firewallD i installed iptables as service at almalinux in order
entries of open ports to not...
Peter I think you mean firewalld along with plesk-firewall service that both write to iptables
Some providers install correctly plesk with almalinux and firewalld is disabled while all needed ports are already at iptables
via plesk firewall, at others firewalld is enabled with open only ssh...
Thanks for reply Peter
I meant if want to keep safe ip not due to hacked account or something but for legit emails in order to not reach incoming from same ip/email limits at gmail, yahoo etc.
So after reaching limits whole queue will be discarded?
You could just put another 2 checkboxes with...
Article does not exist, but the correct behaviour should be extra mails to not be discarded but to send when limit is open again
So if someone has limit 50 per hour and sends 200 in same hour, all 200 emails to go through after 4 hours
Hi
As had same problems with notifications, i did this
Eg if your plesk server host is server.example.com,
you can go at the zone of example .com and set different _domainkey and dmarc
records for the server.example.com
_domainkey in TXT o=~ (for the subdomain not root domain)
at _dmarc for...
remove [mysqldump} section
at {mysqld}
bind-address = 127.0.0.1 # or ::
comment skip-name-resolve with #
this config work at 10 plesk servers with mariadb 10.6
I know but what would be the reason for it
10.6 mariadb comparing to 10.5 has the diference that skip name resolve should be disabled and bind address to be :: or 127.0.0.01 (in case where there is no 2nd admin @127.0.0.1 is created).
Skip name resolve diasb;ed is a performance case but can...
Using the root domain eg domain.com for MX is not good at all for users (i think we are majority) who use cloudflare as DNS and proxy. Ips for domain.com and www.domain.com will be cloudflare's ips so no connection can established to mailserver.
So can use mail.domain.com or smtp.domain.com...