Search results

Adding this to the NGINX configuration could solve your problem.

Thank you for checking this issue. I removed the modsecurity rests and found also modsecurity-files in each /var/www/vhosts/sytems/xxx.domain.tld/conf/ Just to complete the information. I removed all files with an impact to nginx and it works. Now the error has gone.

Thank you for the confirmation that it is used for internal com. Then I‘ll leave it unchanged.

My ssl.conf file in /etc/nginx/conf.de/ contains the following: Why do I have the old and weak TLS-versions TLSv1 TLSv1.1 automaticly installed for proxy_ssl_protocols. Does this make sense or can I remove it?

After some problems with Modsecurity I removed it using Plesk installer (web interface). This seemed to work and now it is indicated as removed However in /etc/nginx/conf.d/ modsecurity.conf still exists with the following content: So it says Modsecurity is on and receives the configuration...

I just got an update to some features of Plesk including fail2ban. Now it seems to work! Thanks to you and to the developer for the quick solution!

I will do so and I've sent you a pm with a proposal how to proceed.

The Plesk Obsidian 18.0.63 Update #3 tonight did not help. Trying to configure fail2ban through plesk UI led again to error 500 together with the message: [plesk-one-week-ban] would be missing. To solve this error I added to the new jail.local the following entries where [XXX] stands for you...

Now everything works fine also the manual banning feature! Thank you for your help!

Cool, this helped! Thank you.

I have read the article but hesitate to use this recipe until I have found out which domain/subdomain is meant by domain_id=28 in my case. What do I have to do to get more information about ID=28 before I delete belonging entries in the plesk-DB?

Thank you, I`ll report if I succeed with this information.

To give the developers an additional input. I suppose, that in my case the following influenced the upgrade. On an earlier stage I used modsecurity. During the installation also a modsecurity jail was added to plesk.conf. Due to some reasons I had to remove modsecurity but the jail of fail2ban...

Thank you for this hint. In my case grep -R plesk-one-week-ban /etc/fail2ban/ does not bring up something except my own and new modifications to get fail2ban work. In addition I do not find a filter called plesk-manual.conf Could you please also provide the content of this filter, too? Then I...

Suddenly after upgrade to Plesk Obsidian v18.0.63 I found this error message in the Plesk protocols: Attempt to change status of non-configured mail service. [domain_id = 28] How can I solve this?

To get access again you could try to add this to your jail.local: [plesk-one-week-ban] enabled = false Probably you will get then another error, what you can solve in a similar way by adding [plesk-permanent-ban] enabled = false (Do not forget to restart fail2ban after modifying the...

Thank you for your attention but I didn't contact your support. Instead I switched back to the old version of fail2ban, as the re-installation (plesk installer --select-release-current --install-component fail2ban) did not work as expected. I.e. only the directory /etc/fail2ban had been created...

After reinstallation of plesk-fali2ban no files are available in /etc/fail2ban . I am currently using the old version again but I cannot manage it using the plesk panel as the error appears as described above.

Anything else?

Since the update to Plesk 18.0.63 trying to open from the Plesk UI via tools/fail2ban results in an error: f2bmng failed: ERROR:__main__:No section: 'plesk-one-week-ban' Trying the solution from...