Search results

@michela.d No, not yet. And I think it's not possible. Maybe it needs a feature request for Plesk.

@rocketchef Unfortunately no, the problem persists. I will try again when I upgraded to Ubuntu 22.

Maybe your provider was blocked by spamhaus and cannot access the DNSBL. That's the case for Hetzner, for example. EDIT: Or this is the problem: Stop using zen.spamhaus.org as a DNSBL example on the Mail Server Settings page

I use Outlook and it has a spam filter, but the mail was detected as spam and sent to the spam folder before Outlook, on server level. So this cannot be the reason. Concerning the second mail (which is the spam report containing the first mail): There is no return-path in the header. I guess...

The help article is referring to the old version of the firewall extension. That's all, it's just outdated.

Recently I got a an e-mail message which was detected as spam by SpamAssassin, although it's obviously no spam. See the relevant parts of the header: [...] X-Spam-Status: No, score=-91.8 required=50.0 [...] [...] Authentication-Results: myserver.example.com; dmarc=pass (p=QUARANTINE...

Sounds like you need the command from the changelog: Change Log for Plesk Obsidian

I use a custom port for Plesk (something like 12345) and upgraded from Plesk Obsidian 18.0.52 Update 3 to 18.0.56 Update 1 and now I have two problems, which were not there before the upgrade. 1. The Plesk mobile app (Android) does not fully work anymore. While the first page in the app still...

Probably you mean "libapache2-mod-security2" instead of "libapache2-modsecurity" (because the first one is in my error message). But no matter whether I use dpkg or apt to remove "libapache2-mod-security2", this package is not installed (this is also the case for "libapache2-modsecurity")...

I'm trying to activate the Atomicorp (basic) ruleset in ModSecurity within Plesk. I got several different error messages within the last months (and I was not the only one, there are many threads about problems), but meanwhile it seems that this is the only message which prevents me from using...

@Alfonzo12 Did you have any success concerning this? I still cannot activate the Atomic ruleset. I followed every suggestion from this thread, from my thread (see link in post #3) and the support article (link in post #2).

I hoped it solves the problems, because my current problem is there since the error message from "apt update". I thought when updates can be downloaded again, there will be a fix. When I had the Comodo ruleset activated some time ago, because Atomicorp was not compatible with Ubuntu 18 then (in...

Maybe you can reboot the server in rescue mode and then you can access it to view the logs.

Unfortunately this does not resolve the current problems with the Atomicorp rulesets. Maybe it will not be fixed for Ubuntu 18, as it's EOL since 1st of May 2023. So I will disable Modsecurity until I upgraded to Ubuntu 20 or 22 (I won't use the Comodo ruleset, as it's too strict for my...

It seems like this is not possible with Plesk, so I will backup this directory via my own script and a cronjob. Probably it's also safer, because the directory is not revealed to the public when it's not symlinked in the vhost folder (although it's always blocked via a .htaccess file). So this...

@trialotto After creating the .list file with the content you posted, apt update produces this error message: E: Malformed entry 1 in list file /etc/apt/sources.list.d/atomic-common.list (URI parse) E: The list of sources could not be read. The content is: deb [arch=amd64...

I have exactly the same problem. See also this posting and the following ones: Issue - ModSecurity/AtomicCorp: Get rid of "N: Skipping acquire of configured file [...] doesn't support architecture 'i386'" (apt update)

I just found this article, which describes the error message I get when starting Apache...

(Sorry, the short edit time already expired) OK, it should be "ubuntu/bionic" instead of "ubuntu bionic". But why does Plesk now inserts this mistake? Or is it ModSecurity itself?

Was there any change concerning my original problem (see first post) today or yesterday? Because now I get this error: W: Conflicting distribution: https://updates.atomicorp.com/channels/tortix-common/ubuntu bionic/amd64/ InRelease (expected bionic/amd64/ but got ) The file...