Recent content by trialotto

@macadia Given this text I think that you have an entirely different issue : "human error" or "human intent". It makes no sense for any hacker to attempt a hack on one account (as you describe it, "an account") and when being succesful, being satisfied with the hack of one account and the...

It is also possible to add ModSecurity at the Nginx level. In most cases, this is a better "security approach" since it prevents bad traffic from reaching the Apache level. Nevertheless, there is general consensus that the ModSecurity at the Nginx level is not to be preferred due to...

I applied a similar approach for testing purposes : a modified SpamAssassin config ....... but it did not make any difference (to be honest, it reduced the spam related issues, but in comparison to DKIM implementation, the "heavy SA config" effects were modest). I currently assume that there...

@macadia @Kaspar is fully right and I highlight the parts of his response that I hope to add value to : In essence, Roundcube is safe and plugins might help. Nevertheless, one could also consider a set of Nginx based rules that add to the default Nginx webmail config. Brute force...

@Kaspar There is a systematic issue with Plesk mail delivery that is not related to "spam" at all. One can add all Plesk extensions and all spam solutions and still spam will go through the Plesk server. I did not find any conclusive / unambiguous root cause of the problem yet ...

@AK_learner Do you have SPF, DMARC, DKIM and alike properly defined? The Plesk mail eco-environment is a bit buggy at the moment, with a lot of spam related issues that can cause major email delivery issues. Nevertheless, simple solutions like DKIM often seem to help in a considerable way...

@La Linea You can and you should. Simply replace the certificates with new ones that do not contain OCSP rules AND remove all Nginx ssl_stapling related directives. The can be related to (insufficient) privileges, but if I am not mistaken, then the command should be limited to domains...

@Janko Falli The statement is not entirely correct, in a number of ways. First of all, Plesk GUI should not "read" Nginx config and can hence not "reflect" that Nginx config. If and when you get a green "UI indicator" by adding lines to the "Additional Nginx directives" .... and it...

@wolle @Raul A. is right. I think that you should first check your Fail2Ban and Firewall for the 18.203.120.118 and 52.30.104.252 IPs (and other IPs associated with Plesk updates). If one of the IPs is blocked somehow, just unblock them : remove them from the Firewall and/or move to...

@snIP3r The error message is highly indicative of the fact that your old license was Web Host, whereas your new license is Web Admin. One could go through all kinds of fuzz and manual steps, but I would recommend to 1 - request a trial Web Host license for migration, 2 - restore the...

Should the second export PATH=/opt/plesk/php/8.3/bin:$PATH not be export PATH=/opt/plesk/php/8.2/bin:$PATH ?? Stated differently, there seems to be a version typo once. Kind regards.... PS Still not sure whether this whole setup with Litespeed is worth the effort. However, pretty sure...

@tertek, It should never be supported, otherwise the attack surface would increase considerably by allowing (too much) access - code injection would be possible. Nevertheless, I do understand your demand for "automation" of Nginx configuration. At this moment, there are two methods to...

@Woutuit To be honest, not that I am aware of. That is, I am aware of some very very "dirty workarounds", but it is better to not elaborate upon that - for many reasons. If you need a migration in general sense, then it is often recommended to wait until the bug fix has been applied to an...

@Woutuit, It is not an issue about Debian support, as @Sebahat.hadzhi already correctly explained. The Migration Manager had (and still has) some bugs that are not solved in a timely manner and this "Failed to deploy Python on source server" is one of them : the Migration Manager failed...

@greedysoul The workaround suggested by @PeopleInside should work, but it still is not a solution - it is a mere workaround of an issue. An alternative workaround is to set your system time one hour later or earlier : this barely has impact on your system, but it will resolve the PUM issue...