Recent content by Sebahat.hadzhi

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

Hey, guys. Thank you for your input. While there is no dedicated built-in feature to copy plugins, I believe there's a relatively simple workaround. If you add the manually uploaded plugin to a set, you should be able to easily install the plugin(s) for additional websites. @pleskpanel can you...

@absaad , could you please examine the processes running at the time of the issue occurrence as suggested by hschramm earlier in the thread and share the details here?

At this point, there are no plans to integrate FrankenPHP into Plesk. You should still be able to install and configure it on your servers. I would like to encourage you to submit your feature request here.

Thank you for your input. We forwarded it to our backup developers for further review. I will follow-up with more details as soon as possible.

@c59933290 , if the auto-login to Plesk no longer works, it will be best to get in touch with the administrator of the server, so they can check further what's causing the discrepancy. It is very unlikely for the issue to be caused by Plesk itself, but rather the autologin configuration.

@LRLD , thank you for the update. The behavior was indeed recognized as a product bug identified with ID PPPM-15074. At this point, the only workaround is to manually recalculate the statistics either by using the refresh button or by running: plesk sbin statistics --calculate-one...