Recent content by EugeneKazakov

Thank you for reporting the problem. The issue happens with PHP-FPM starting with 8.2 version because of the changes in its configuration testing utility: Fix bug #68591: Configuration test does not perform UID lookups by bukka · Pull Request #10165 · php/php-src We are working on a fix to make...

I'm happy to hear it. I would appreciate it if you post the fragment from the log file. It could help us to find the root cause of the issue.

Have you tried `systemctl restart plesk-task-manager`? Could you please send the output of the command: sed -ne '/START plesk-task-manager/,/STOP plesk-task-manager/ p' /var/log/plesk/install/plesk_18.0.*_installation*.log

Please check the version of the following package: # rpm -qa | grep plesk-task-manager plesk-task-manager-18.0-2.centos.7+p18.0.36.0+t210604.1022.x86_64 In case the version is different (e.g. p18.0.35), you need to install missing updates, i.e. run `plesk installer update` In case the version...

The idea of the temporary hostname is exactly to have a valid certificate for the address. When Let's Encrypt extension is installed (a typical configuration), a certificate is expected to be issued. Could you please help us to find the reason for the failure: why did the certificate request...

Yes, you are right.

Moreover, the process is very gentle and does not update all Plesk instances as soon as possible. We are trying to spread the audience during the month, starting with a small portion and growing the daily rate.

Oh, I thought the issue is with automatic updates, but it is even worse. Just in case, don't you use any mirror for autoinstall.plesk.com? ping autoinstall.plesk.com should reach one of the servers *.cdn77.org Check the file /root/.autoinstallerrc - it might store the SOURCE variable.

Are you sure the checkbox "Automatically install Plesk updates" is enabled on this server?

We have not started rolling out of the automated updates for 18.0.25 yet. We are going to do it on Monday after the first minor update 18.0.25.1 is available. In your case, the automated update is expected only the next Friday. However, you can perform a manual update.

Could you send me an IP of the server, which did not receive the update?

Sorry for this inconvenience. I confirm there was a bug with the queue for automatic updates: we checked the schedule too late and the first batch of servers started the update disregard the allowed time frames. In further updates we won't repeat this mistake.

It must be a bug. Could you provide the IP of your server?

BTW there is modern REST API based on JSON and OpenAPI: About REST API

The only known difference between a new installation of Obsidian and an update from Onyx is that the feature of access to Plesk with 443 port should be disabled for backward compatibility after the update. I would recommend trying to switch on / off with CLI. More info in the docs: Customizing...