Search results

SSL received a weak ephemeral Diffie-Hellman key: how to solve this problem

https://talk.plesk.com/threads/18-0-34-code-editor.360126/

Hi all, We did submit a bug for this under the ID PPPM-12860, we plan to fix this in an upcoming update

Do try it over SSH: plesk bin license -i ACTIVATION_CODE

> [2021-02-14 13:49:49.897] ERR [panel] DB query failed: SQLSTATE[HY000] [2002] No such file or directory: This looks like MySQL being down, check the service and mysql log but that should not be related to the original issue

Probably your server does use NAT, so the IP of your Server is 10.15.0.7 and then outside your server your provider does route the traffic over 104.248.1.x This is quite normal in most Cloud providers, and many VPS

Plesk does not update certain Packages, as they will require a reboot (Kernel, etc.) You can update them manually over SSH

Any additional errors in the panel.log? What OS and Plesk version are you using?

You can click on the Hosting Settings of the subdomain and select the SSL that you want there.

do you have nginx installed? if yes do: # plesk sbin nginxmng -d && plesk sbin nginxmng -e this because apache does try to bind to 80 and something is already bound to 80 (probably nginx) in such case apache should be on 7080 and not 80

https://YourPleskURL:8443/v2... or https://YourPleskURL:8443/v1...

As the warning says OWASP is extremely strict :) Good to know you were able to fix it

Ignore the warning and upgrade with the file there

Did you change it to 1200s like in article? Depending on your internet speed you may need to increase it even further. Also, as you are editing it over /usr/local/psa/admin/conf/php.ini make sure to access plesk over the 8443 port and not an custom URL without port. Or you can do it like this...

Any errors in the Roundcube logs? /var/log/plesk-roundcube/errors

Hi @hillcow do you mean this one? Or what do you mean with "Scheduler" page ?

Yes, it was: https://docs.plesk.com/release-notes/obsidian/deprecation-plan/ cgroups or lve can be used as replacement

@321GROUP you can install a custom PHP version with the outdated PHP, but I would not recommend it as you will put all your customers at risk. If you want to keep that 14 Customers I would recommend setting but some small server with CentOS 7 and leave these 14 customers isolated there, this way...

Check if you have "Apache restart interval" enabled if yes you need to wait that time until it takes effect. If not then check for any HTACCESS or custom config that does overwrite it

It should have permissions like this: select * from user where user='admin' \G *************************** 1. row *************************** Host: localhost User: admin Password: ??????????????????? Select_priv: Y Insert_priv: Y Update_priv: Y Delete_priv: Y Create_priv: Y Drop_priv: Y...