Search results

Hello, @papahausa . Could you please confirm the MariaDB version on your server and share the content of the /etc/my.cnf file?

Hello, @Thomas Oryon . As mentioned, by @scsa20 , the EPEL repository is required. Since your server is not connected to the internet, the connection to the repository fails. What you can try is creating a local EPEL mirror repo on another server with internet access and transferring it to your...

No, I am afraid this goes beyond my expertise in this area. I am sorry.

Thank you for the confirmation, @tristansilkstream . The behavior indeed has been recognized as a bug identified with ID PPPM-15067. The ETA for the fix is the upcoming Plesk release (17.0.72). Until the fix is released the workaround we can suggest is: 1. Commenting out the...

Hello, @realaaa@ . If those are genuine login failures, you can always increase the limit if the default value is causing issues on your environment by editing the panel.ini file: [security] bruteforceProtection.enabled = true bruteforceProtection.rateLimit = 5...

@tristansilkstream . Thank you for the further clarification. I was unsuccessful in replicating the behavior with the duplicate directives, but I am positive this is root cause of the issue. Can you run the following command on your server, please: plesk db -e "SELECT value FROM TmplData INNER...

Hello, Brendon. This is still not considered a vulnerability, because the account credentials that are exposed have no harmful permissions. Only anonymized technical data is gathered and sent via these credentials. Nevertheless, our team is currently reworking the manner in which keys are...

@nethubonline , I believe this also applies for subscriptions, but to be certain I will confirm with our team and follow-up once I get an update.

@Gamingmate92 , can you please try running the following commands to ensure the root user has the necessary privileges: plesk db GRANT ALL PRIVILEGES ON mysql.* TO 'root'@'localhost';

@rexplorer , have you already checked Kaspar's suggestion about the PHP mail function being disabled on the server?

Hello, Angelo. As far as I can see, this error results from corruption in the MSI subsystem: https://www.thewindowsclub.com/msigetproductinfo-failed-to-retrieve-productversion If contacting Microsoft to fix the subsystem is not an option, what you can consider trying is restoring the server if...

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 license from a reseller, your reseller is in charge of providing you with support. You can raise the inquiry with...

As suggested by @scsa20 already, the issue is very likely related to SELinux. Please try the following solution: https://support.plesk.com/hc/en-us/articles/12377015098903-Unable-to-access-website-hosted-in-Plesk-Server-Error-403-Forbidden-or-Apache-default-page-is-shown

Hello, @Rabah . Considering that the source server is EOL issues could be expected. It is very unlikely for a patch to be released for that outdated version even if the root cause lays within the migrator. There was a similar bug that was fixed in version Migrator 2.26.11.

Hello, everyone. Our team got in touch with Dr. Web. At this point, Dr. Web is still reviewing the matter and I cannot confirm what actions will be taken. The only workaround, we can suggest is still changing the update server.

If I correctly understand the inquiry and you want to upgrade from Ubuntu 20 to 22, you can use Plesk's automatic dist-upgrade tool: https://support.plesk.com/hc/en-us/articles/12377714344983-How-to-perform-dist-upgrade-procedure-on-Linux-server-with-Plesk

@seppi , if that issue still persists, could you please confirm if you have Proxy mode enabled in Domains > example.com > Hosting & DNS > Apache & nginx?

Hello, @JayJay69 . Could you please confirm if the error is still occurring? It could have been caused by a temporary connectivity issue.

The issue was caused by a bug (EXTPLESK-9187). It has already been solved in the latest version of the Laravel extension. As already suggested by @Kaspar , please proceed with the extension update.

Apologies for the delayed response. I wasn't available during the past week. If the issue still persists, please try moving imunify-testing.list.example to some other location, for instance: mv /etc/apt/sources.list.d/imunify-testing.list.example /root