Search results

Thank you. Everything appears in order. Could you please confirm what's the Plesk version and the OS + version of the server related to the issue?

@chris-design , there is still no clarity on the reason for the issue. According to the escalation to Dr. Web and their engineers debug mode should be enabled to gather more details in order to identify the issue:

@se2e-dev , regarding the first error are you experiencing any issues accessing the Monitoring dashboard? Also, can you confirm how many websites approximately you have configured under it? As for the Imunify entry, could you please confirm what type of notifications are currently enabled in...

@absaad Assuming that you are Linux user, you can limit I/O on Plesk-level through Cgroups manager.

@iozuniga , could you please run the following command on your server and let us know what the output is: ls -la /var/lib/sw-cp-server/proxy

@rexxxx , I am not sure if that will help in your case, but you might dive it a try if you wish.

Hello, @rexxxx . Could you please describe in more details what happens when you attempt to access the Backup Manager? Is there any error returned? Also, please check /var/log/plesk/panel.log and let us know what's being logged at the time the issue occurred.

@iozuniga , have you tried re-installing the extensions? Often, the error could be caused due to a corruption.

@PercyDwn , could you please make sure that outgoing connections from the IP addresses are allowed according to this article: https://support.plesk.com/hc/en-us/articles/13303706286999-What-IPs-should-be-opened-in-the-firewall-to-connect-a-server-to-Platform-360

Thank you for the update. Could you please confirm if there's any antivirus extension currently installed on the server?

If there are a certificate assigned it was likely non-existent or corrupted. If there wasn't, I am also unsure what caused the issue.

Apologies for the misunderstanding and thank you for the clarification. I brought that to the attention of our team and they agree it should be improved. However, at this point, I cannot provide an ETA on when that will happen. I will follow-up with confirmation when there are more details.

Hello, @Fede Marsell . I will double-check with our team how to disable the option and I will follow-up with confirmation as soon as possible. Thank you in advance for your patience in the meantime.

@kenthan , is that server indeed running Plesk Obsidian 18.0.72 Update 2? If not, I would suggest updating to the latest version. If the issue still continues temporarily enable Plesk debug mode, replicate the issue and re-check the /var/log/plesk/panel.log file for additional entries.

Thank you for the update. Could you please try uninstalling the extension, so if there's any corrupt data it would be removed? plesk bin extension --uninstall dnssec and then re-run the installation command: plesk bin extension --install dnssec

Hello, @sub205 . Could you please navigate to Subscription > example.com > Hosting Settings and confirm if there's a certificate selected under Certificate within the SSL/TLS support section? If there is, please set it to "Not selected" and try accessing the SSL page again.

Can you please also try adding the additional directives according to this guide: https://support.plesk.com/hc/en-us/articles/12377655871767-Plesk-site-unavailable-502-Bad-Gateway-upstream-sent-too-big-header-while-reading-response-header

Thank you for the confirmation. I know that changing the time of the daily task cron job helped for some users reporting a similar issue. Thus, I will recommend giving it a try.

@kenthan , could you please check the /var/log/plesk/panel.log for additional details? Meanwhile, you could try manually installing the extension by running the following command via the command line: plesk bin extension --install dnssec

@vincenzo.casu , can you please try manually running the daily task and confirm if it returns the same error: plesk daily -f InstallSystemPackageUpdates