• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Clean Install Ubuntu 18.04.1 / Plesk 17.8.11 - Errors

learning_curve

Golden Pleskian
Despite the thread title, it did actually go very well :)

However, we have two specific Plesk related errors, which we need to fix, before customising Plesk ourselves and then swapping over all our live domains / data etc from our existing CentOS server.

1) We cannot add the MagicSpam Extension. It's not installed by default, so when selected via the Add or Remove Components Plesk GUI and an attempt is then made to add it, there's a misleading error message shown (pics). We're guessing that this message maybe referring to Plesk's SpamAssassin (?) which is found under Mail Hosting but the two are different. It's possible to run both anyway, as we do already in 17.5.3 where the MagicSpam Extension & Spam Assassin both work perfectly. Maybe @MagicSpam12 can offer some advice too?

Plesk Installer 1.png Plesk Installer 2.png

2) We cannot enable Web Application Firewall (ModSecurity). The GUI error is this:
Code:
Failed to install the ModSecurity rule set: modsecurity_ctl failed: gpg: directory '/var/lib/plesk/modsec/.gnupg' created gpg: keybox '/var/lib/plesk/modsec/.gnupg/pubring.kbx' created gpg: /var/lib/plesk/modsec/.gnupg/trustdb.gpg: trustdb created gpg: key FFBD5D0A4520AFA9: public key "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" imported gpg: Total number processed: 1 gpg: imported: 1 gpg: assuming signed data in '/tmp/tmpJh9B3q/aum' gpg: Signature made Mon Jul 23 17:43:44 2018 BST gpg: using RSA key FFBD5D0A4520AFA9 gpg: Good signature from "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 1818 66DF 9DAC A40E 5B42 9B08 FFBD 5D0A 4520 AFA9 TERM environment variable not set. Command '/bin/bash < /tmp/tmpJh9B3q/aum' returned non-zero exit status 1 Unable to download tortix rule set
and the panel.log error is this:
Code:
stderr:
gpg: directory '/var/lib/plesk/modsec/.gnupg' created
gpg: keybox '/var/lib/plesk/modsec/.gnupg/pubring.kbx' created
gpg: /var/lib/plesk/modsec/.gnupg/trustdb.gpg: trustdb created
gpg: key FFBD5D0A4520AFA9: public key "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: assuming signed data in '/tmp/tmpJh9B3q/aum'
gpg: Signature made Mon Jul 23 17:43:44 2018 BST
gpg:                using RSA key FFBD5D0A4520AFA9
gpg: Good signature from "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1818 66DF 9DAC A40E 5B42  9B08 FFBD 5D0A 4520 AFA9
TERM environment variable not set.
Command '/bin/bash < /tmp/tmpJh9B3q/aum' returned non-zero exit status 1
Unable to download tortix rule set
The relationship between Plesk and Atomicorp does seem to be a 'fiery' one ;) as we've seen quite a few errors before in 17.5.3 but these have then been fixed a few days later via a Plesk upgrade / knowldege base fix. We have searched for and tried any similar errors / fixes found in the knowledge base, but currently none of those will fix this one.
 
No answers yet for the above ^^ Hopefully some maybe along from Plesk soon :)

Meantime, another Plesk related error, but this time only when attempting to use the Plesk Migrator extension in 17.8.11. Migration (incl Plesk to Plesk) is well explained in THIS up to date knowledgbase article, but we can't get past this error:
Code:
Failed to connect to target Plesk server by Plesk API: <urlopen error [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:726)>
We're TLSv1.2 only on both servers (i.e. no support for TLSv1.1 or earler) but surely the latest Plesk extension release, which runs on the latest Plesk release 17.8.11#16 can't be limited to TLSv1? Hopefully that's just a red herring. Anyone from Plesk?
 
Any thoughts / comments / suggestions from Plesk with regard to these errors? o_O We can't really move on until we've fixed them....
 
Meantime, another Plesk related error, but this time only when attempting to use the Plesk Migrator extension in 17.8.11. Migration (incl Plesk to Plesk) is well explained in THIS up to date knowledgbase article, but we can't get past this error:
Does it work correctly on your Plesk servers with default TLS configuration? I mean without your well known multiple TLS customizations?
 
Regarding the situation with MagicSpam extension, there was corresponding discussion on forum. I have no any additional information.
If you think that you found Plesk bug, please report it here Reports and developers will check it.
If you need fast solution - please contact Plesk Support Team.
 
Regarding the situation with MagicSpam extension, there was corresponding discussion on forum. I have no any additional information
Okay thanks. We had looked before posting, but couldn't find anything that included all three i.e. Ubuntu 18.04.1 / Plesk 17.8.11 #16 and MagicSpam plus there has been no reply from @MagicSpam12 on this, which is unusual... o_O
If you think that you found Plesk bug, please report it here Reports and developers will check it.
If you need fast solution - please contact Plesk Support Team.
Again okay thanks. We'll post the answers in due course. We're guesing we can't be the only users affected, as these errors are all before we've made any Non-Plesk provided, changes (of Plesk itself)
 
Great support direct from Plesk :)

MagicSpam? That is quite a simple answer and is shown HERE

ModSecurity? That was also a simple answer really.
Atomicorp do not support both Debian 9 and Ubuntu 18.04 - Yet... ;)
We are going to park this one until they do and then Plesk do, shortly afterwards

Migration? We're on with that now....
 
More useful data direct from Plesk in addition to the last post

MagicSpam? More relevant information is shown HERE

ModSecurity? More relevant information is shown HERE

Migration? We're still on with that one....more when we have it
 
Migration? Well, yet more outstanding service direct from Plesk :cool:
This time it was a bug, for which they have now provided a workaround and the bug will be properly fixed with a future release.
The workaround is HERE
We can finish all of our migrations / checks / tests now and then start working, only on our Ubuntu server once this is all complete :)
 
Back
Top