Search results

Thank you for your patience, @ivanes82. Unfortunately, I was unable to reproduce the reported issue on the test environment. The SELinux mode remained intact and set to enforcing. If you have the option, please submit a ticket with our support team so they can further investigate the issue and...

@forzasalva Could you please check if you have an .htaccess file with Cache-Control policy for the website in question?

Could you please confirm what are the local MariaDB/MySQL Settings as well?

Understood. Thank you both for the feedback, it is highly appreciated. I am sorry for the inconvenience this change caused you.

@laurentakn, please try:

Hey, @oskar.szafraniec. The case is no longer in the backlog, it is currently in the queue. However, I still cannot provide any ETA on when a fix will be delivered. What Kaspar mentioned in his last reply is still true. There aren't many users affected and the priority is not considerably high...

Hello, @JulianDot. There is no ETA I can provide at this point, but I will update the thread with more details as soon as possible.

Thank you for the confirmation. I reopened the report for further investigation. I will update you with more details shortly.

Thank you for the update. I have configured a test environment with AlmaLinux 8.10 and Plesk .65 #1 with Atomic daily ruleset updates. I will check it tomorrow and further discuss the case with our team if the same behavior is observed.

Hello, @ivanes82. According to Atomic's team running aum -u should not touch SElinux. Could you please try updating the aum package by running the following command: After that you may check ausearch log after re-enabling the Atomic standard rule set at Tools&Settings > Web Application...

Hey, @galaxy. Could you please confirm the OS of the server?

Hello, @nethubonline. This is a known issue identified with ID PPPM-12992 and is has been investigated by our engineers already. The conclusion is that the root cause is pretty complicated and a fix has not been introduced yet. Systemd and firewalld.service, fail2ban.service files involved...

I understand how how users' confusion could lead to unnecessary frustration and spike in support requests. I forwarded the feedback to our release management team. I talked with the SiteJet team and we have not observed a similar malfunction. Do you think it is possible for those users to have...

Thank you for the details, Carlos. I can see the domain name in one of the screenshots you provided and it looks like the same is pointed to Cloudflare by nameservers. Could you please confirm if you synced the DNS zone already and if the SPF/DKIM records are present in the Cloudflare DNS zone?

It could be difficult to fully anticipate such changes even with beta testing, especially when multiple software components are involved. To be frank, I am not entirely sure how was this overlooked, but it will be certainly addressed further.

Hello, everyone. This is just an estimate, we will do our best to release the fix earlier than that. In the meantime, the workaround we can suggest is: Connect to the server via SSH. Navigate to this directory: Create a backup copy of the pmm-ras file using the following command: Remove the...

Thank you for the update, Peter. Our engineers are currently working on resetting signature calculator before archive flush. The ETA for the hotfix release is the 25th of November. Of course, the team will do their best to release it as soon as possible.

Hey, @Colonel36. One of the simplest ways of creating a backup of your WordPress files + database is directly through WP Toolkit. Detailed instructions you can find here. I hope that helps.

Hey, @pml_orion, could you please double-check the rule and confirm if the passive port range is 49152-65535? You might also want to double-check the instructions in this article. I hope that helps.

@nmdpa3, thank you for the feedback. I will forward it to our team for review and possible consideration.