• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Question ModSecurity Error

Zoo3

Regular Pleskian
When I logged in to Plesk, ModSecurity errors have been warned of last week.
How can I resolve the errors below?
Is this a ModSecurity side or a Collabora Repo side? I tried recreating Collabora Repo. I was able to update with yum update without problems.

Error: ModSecurity an attempt to update the rule set failed. modsecurity_ctl failed: gpg: key KEY-ID: "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
gpg: Signature made Thu Jun 21 00:13:55 2018 JST using RSA key ID KEY-ID
gpg: Good signature from "Atomicorp (Atomicorp Official Signing Key) <[email protected]>"
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: FINGERPRINT CODE
TERM environment variable not set.
https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-centos7/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

This itself exists.

Please help.
 
Back
Top