Search results

Thank you for the provided details. Our team recently published an article about this issue and the same is caused by a bug in MariaDB as their packages are not fully compatible with the system SELinux policy.. Please find the details and the workaround here...

@safemoon , I am unable to replicate the issue with the following query: curl -k -X DELETE -u root:pass -H "Accept: application/json" "https://plesk.example.com:8443/api/v2/domains/1"

I cannot confidently confirm whether the options you are planning to add won't cause any conflicts. Regarding the spoofing issue, maybe this could help: https://support.plesk.com/hc/en-us/articles/12377380746903-How-to-protect-a-Plesk-mail-server-against-mail-spoofing

Thank you for the update and confirmation. Unfortunately, I am not sure what might be causing this specific issue. I would suggest opening a ticket with Plesk support for further investigation on your server. To sign-in and open a ticket please go to: https://support.plesk.com If you got your...

Hi, @Dmytro . What I can suggest is trying to uninstall ModSecurity and then re-installing it. Also, you might try switching "Run rules on" from Nginx to Apache or vice versa.

The error in question indicates that Plesk was unable to connect to the MySQL service. As far as I am aware, this often happens if there's interruption of the database service. Could you please check the status systemctl status mariadb and confirm if there is any correlation between the running...

@pleskuser67553 , a fix for the issue was introduced back in Plesk Obsidian 18.0.68. For what is worth, I can no longer replicate it on a fresh AlmaLinux 9.6 environment. Can you please open a new bug report with more details on the issue you are experiencing and steps to reproduce it? Thank you...

Hello, @RalfMeyer . Does curl -I http://our-mirror.domain.tld/pool/PHP_7.1.33_16/php71-deb11.0-x86_64.inf3 also return 404, please?

That does sound like a valid point. I will ask our team to re-check the case with that in mind.

I am glad to hear the workaround helped. It is a product issue (PPPM-13576). When TLSv1 is disabled for Plesk service the proper operation of Premium Antivirus is prevented.

@se2e-dev , an official fix for the bug has not been introduced yet, unfortunately. What I suggested in my previous reply was just a workaround that could be applied until the bug is permanently fixed. Could you please try repeating the steps: Connect to the server via SSH Backup the psa...

Thank you for the confirmation. Please try creating the file with the following content: server { listen [::1]:8443 ssl; listen 127.0.0.1:8443 ssl; include /etc/sw-cp-server/conf.d/*plesk-drweb-local.ipv6.inc; ssl_certificate /opt/psa/admin/conf/httpsd.pem; ssl_certificate_key...

Hello, @FYI . Thank you for your input. I opened an internal case with our Docs team (ID DOCS-3236) for further review and consideration of your suggestion. I will follow-up with more details as soon as possible.

Hi, @q-quan . Could you please confirm if there's a /etc/sw-cp-server/conf.d/plesk-drweb-local.conf file on the server? Thank you in advance.

Thank you for the confirmation. Could you please still double-check if any of the following files exist on the server and contain invalid credentials: /root/.my.cnf /etc/mysql/conf.d/client-mariadb.cnf /etc/mysql/debian.cnf

@SFonoyet , have you tried the solution from the following article: https://support.plesk.com/hc/en-us/articles/12377849511447-Plesk-upgrade-installation-migration-fails-Access-denied-for-user-admin-localhost

The issue with the underscore parsing should be fixed. Now the reading function won't overwrite its own value. If you still encounter similar behavior, please let us know.

Hi, everyone. The issue with the underscore parsing should be fixed. Now the reading function won't overwrite its own value. If you still encounter similar behavior, please let us know.

I know that similar issues have been caused by Cloudflare. In this article, there's a section "Accessing a website / webmail using a local hosts file" - that will allow you to force the domain name directly resolve on the server bypassing Cloudflare. Could you please temporarily add the entries...

Along with @scsa20 's suggestion, I would also like to ask whether the domain name is routed through Cloudflare by any chance?