Search results

Thank you for the update. I am not quite sure what is causing the issue in this particular case. 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...

@se2e-dev , the issue is related to the vulnerability database structure. The command should update it and consequently lead to the task is finished successfully every time it runs. No, no additional adjustment should be needed once the fix is released. Yes, of course. However, at this...

The issue is caused due to a bug identified with ID EXTWPTOOLK-10397, which will be fixed in one of the upcoming releases. Until the fix is introduced, please apply the following workaround: Connect to the server via SSH Backup the psa database plesk db dump psa > /root/psa_dump.sql Remove the...

Hello, @Rabah . Can you please try applying the solution from the following article: https://support.plesk.com/hc/en-us/articles/12387591403543-Error-while-performing-a-subscription-re-sync-Failed-to-execute-SQL-query-Login-failed-for-user-sa

@peterpijpelink , thank you for reporting the case. I forwarded it to our team for further review. @Kaspar thank you for jumping in to suggest the ownership change.

Can everyone who is still experiencing the issue on a daily basis confirm what's the time zone set for their servers? As well as the schedule of the cron.daily task: cat /etc/crontab | grep daily Thanks in advance.

Guys, it was confirmed that the workaround previously suggested for the Apache update is indeed causing an issue of ActiveSync and IMAP connectivity with Plesk Premium Email. The workaround we can suggest is: Connect to the server via SSH. Rename the file deployed by the hotfix: mv...

Hello, @UHolthausen . We do have a registered bug on our end identified with ID EXTPLESK-9121. Our team suspects that the root cause might be a bug in Grafana, but the case is currently still under investigation. The workaround, we can suggest is: Open the /etc/grafana/grafana.ini file for...

Thank you for the update, @M_at . Have you also tried manually importing the key as initially suggested in the thread?

Hey, @JuanCar . Have you seen this article: MySQL/MariaDB on the server with Plesk shows the error: Too many open files

Hey, @IT Ufficio Key-One . We have a registered bug identified with ID PPPM-7228 for the SELinux error. It should not prevent login to chrooted environment and these messages can be safely ignored.

Thank you for the update. Does repairing the database with plesk repair db make any difference?

Thank you for your patience, @dleigh . Our team discussed the case with Wordfence and Patchstack and the vulnerabilities should be properly reflected now. Please note that according to them some are not patched yet, but they should properly reflect the plugin version now.

Hello, Paolo. Is that the full error message? Isn't the extension causing the issue mentioned in the message as well? If it's unclear, please check var/log/plesk/PMM/backup-timestamp/backup.log. Once you identify the extension, please try reinstalling it. Afterward, run the following command to...

Hey, @ThinkYEAH . The issue you are describing is different compared to the one reported in the thread - Plesk panel returning error 500. If I understand correctly, your issue is related to the admin user of xenForo rather than Plesk itself. If I am right, please open a new thread. Also, please...

Hey, @theplaza . Please run apt-get update and let us know if any additional errors are returned.

Hello, @givemesomoney . Could you please check /var/log/httpd/stderr.log and confirm if there are any entries suggesting you hit LSAPI_CHILDREN?

You can directly share it in your reply, you can send me a private message, you can use something like Pastebin, etc. - whichever more convenient for you.

Hello, @IT Ufficio Key-One . Could you please also try restarting the service by running the following command: systemctl restart agent360

Hello, @fabio.florencio . No, this is not on the roadmap. The feature request is being evaluated, but it has not selected for implementation yet. I would like to encourage you to share your feedback and any feature requests/improvement ideas with us here.