Search results

I think I have it, I have run the test on Have DANE? and the results are correct: postfix/smtp [1361244] 2ABC62000CBB38: to=<e00d09fca363f358@dont.havedane.net>, relay=dont.havedane.net[xx.xx.xx.xxx.xxx.xxx]:25, delay=1.4, delays=0.85/0.05/0.35/0.11, dsn=2.0.0, status=sent (250 2.0.0 Ok...

I don't know, I am facing the same difficulties as you in getting the connections verified. My postfix configuration file also did not have the entries to the certificates. I am struggling for my server to use dnssec.

The error you are encountering typically occurs when trying to initiate an SSL/TLS connection on a port that expects a different protocol or handshake method. In your case, you are attempting to connect to mail.leagues-united.de on port 587 using OpenSSL's s_client without specifying the correct...

I installed the update yesterday, and removed my modification, and the problem has been solved. Selinux is no longer disabled when updating modsecurity rules. So at least in my case the problem has been solved with this update.

This has been fixed in the Plesk Obsidian 18.0.66, #2 update. I don't understand the lack of transparency by not publishing it in the log. I think it is important to upgrade to this version, since disabling selinux is quite serious.

I cancelled the automatic renewal before it was due for renewal. Even so it is still active and when I try to buy a new license, it does not let me enter my server id. The subscription has been cancelled. Your license is valid until 2025-01-03 Reactivate subscription License status: active

Don't mind me, today was the automatic renewal, is there any way to change the payment for a plesk plugin from monthly to yearly? I bought atomic monthly to test it, and now I want to change it to annual, but I don't know how to do it.

I am now getting this, and the modsecurity rules are not updated. I have the paid atomic rules. I didn't get to use chattr +i /etc/httpd/conf.d/security2.conf. simply running /usr/sbin/plesk sbin modsecurity_ctl --enable fixed it.

Thank you very much, I will try it.

Running “plesk sbin modsecurity_ctl --status” resulted in disabled. The panel.ini logs set to debug show nothing. As a consequence of having automatic modsecurity updates disabled, because there is a bug that when updating the rules leaves selinux permissive PPPM-14747, I have a cron job that...

I have been noticing for a while that when I disable and re-enable modsecurity, it starts to block malicious attacks, but after a day there is no more ip blocking, and the logs are completely blank. This made me suspicious, and although in the plesk interface modsecurity is shown as active, I...

Thank you very much for your response. It is a bit clearer, but I still have a doubt: is it safe to update those packages manually? If by activating secure updates, they are not updated, I wonder if I should update manually. Thank you very much.

Running sudo yum update from the terminal gives me these two updates: epel-release noarch 8-21.el8 epel 24 k xvidcore x86_64 1.3.7-9.el8 epel 268 k These do not appear in the plesk update installer. Why don't they appear there to update them through plesk and ask if it is safe to update them...

Finally yesterday I was able to contact the plesk support team and told them about my problem. They were able to reproduce it on a test server. They have assigned the bug ID PPPM-14747, and told me that it should be resolved by the next plesk update.

Muchas gracias por la información, ya lo tengo configurado de esta manera, pero lamentablemente hay muchos más correos que se envían con otros correos que no pasan las medidas de seguridad y por lo tanto terminan en la carpeta de spam. Parece que plesk ha dejado las cosas a medias, y ha dado...

This is a really important feature that still doesn't work in plesk and is really annoying. It would be nice to know if while this feature is included in plesk, there is a way to fix it manually. All email acknowledgement emails go to spam, I have also configured that I get email notifications...

Thank you very much, I am waiting to hear from you, to know if I have to contact plesk technical support for a problem in my server or if it is a general error, and I have to wait for a plesk update with the correction. Thank you very much.

Muchas gracias por su respuesta. Al ejecutar aum -u, las reglas se actualizan correctamente y selinux permanece en vigor. Sin embargo, la ejecución diaria de plesk -f UpdateModSecurityRuleSet o su actualización automática todas las noches a través de la programación de plesk hace que selinux...

Can someone please tell me if it is normal that when atomicorp modsecurity rules are updated selinux is set to permissive, and once the update is finished selinux is kept in permissive. Thank you very much.

Can no one really help?