Search results

I think this is an bug. I had this issue on CentOS Linux 7.4.1708 (Core)‬ Plesk Onyx 17.5.3 Update #41 It seems to occure when using a hostname with 2 labels only (e.g. example.com) and preconfigured the server correctly so that "$ hostname" echoes "example" and "$ hostname -f" echoes...

I know that's been a pretty long time. But as Google led me to this post - have you solved this? In Plesk Onyx it's still the same behaviour.

Hi friends, I've found out that certificates created in the server pool are neither listed under the view of the extensions nor they are renewed automatically.

Alright. I think I can reproduce the issue. Certificates added to the server pool by using the "Lets Encrypt" button from within the interface where you can assign certificates for mail and the panel are not beeing renewed automatically.

By the way: the first domain which is mentioned in the error message is deactivated. So it's clear why Let's Encrypt renew fails. But that has nothing to do with the other certificates I'm talking about.

I know that, of course. The both domains mentioned in the error message are failing because they are either not routed to the server or the customer has deployed an htaccess file with a RewriteRule which causes this issue. So it's OK that they fail and they are meant to fail as long as the...

Hi Peter, thanks for getting back to me. I really appreciate this! In my case certificates used for securing mail and plesk itself are not automatically renewed. When I run: /opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/letsencrypt/scripts/renew.php'" I get...

Sorry, but that's not true. I've seen a lot of certificates which had not been renewed due to unclear failures.

Hi, I'm operating Plesk Onyx behind a NAT firewall and have assigned a public IP address to the internal IP address as outlined in the documentation. But I do not want to change the hostname of the server to the PTR of the public IP address as the FQDN of the machine should correspond to its...

As far as I understand starting from version 10.2, Plesk Panel encrypts the Administrator's password before saving it to /etc/psa/.psa.shadow. This avoids saving the password in cleartext to prevent an information disclosure vulnerability for /etc/psa/.psa.shadow if its permissions are not...

Hi, I'd like to understand why the credentials for the MySQL user "admin" are encrypted in /etc/psa/.psa.shadow but the encrypted string itself can be used as the password. $ cat /etc/psa/.psa.shadow $AES-128-CBC$abcdefghiklmnop==$mnbvcxylkjhgfd== $ mysql -uadmin -p`cat /etc/psa/.psa.shadow`...

Hi Igor, do you have got any information from the team, yet? Beside the technical limitation this should also be considered from the point of risk management. Yves

The same issue here on 21 servers which were automatically updated this night.

Thanks for clarification.

The fix works. The bug still seems to exist in Plesk 12.0.18 on CentOS Linux 7.0.1406

Is this the fix for the password decryption bug? If not - is there a Confixx migration assistant in Plesk 10?

Have you been able to fix this issue?

Have you really exspected something different?

Anyone who has a running system or not switched back to qmail yet should NOT try this update. At least not if it's not older than round about 6 weeks. This avoids headaches.

The support resolved my issue with removing mail accounts. The other issues which seemed to be introduced by the support were solved too. Spamdyke had to be reconfigured (smtp_psa, smtps_psa were overwritten) and my ip had to be entered to the lists of accepted ips for administrative login...