Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
Do you have working instance of 17.8.11 and this error appears only during installation of updates? Or maybe you have updated to 17.8.11 recently and this upgrade wasn't finished correctly?
Can you please restart plesksrv service:
net stop plesksrv
net start plesksrv
and then check, that connection to plesksrv is working and Plesk is able to get db password by launching:
plesk sbin psadb --get-admin-password
p.s. Also please check if there were crashes of plesksrv.exe process in %plesk_dir%\etc\crashdumps folder (files should look like plesksrv<something>.dmp).
I got db password successfully.
And i always install update manually using plesk Web control panel.
There was not any crash dump file.
My plesk instance is working correctly but this is the second time that i see this error during update, the last time was while installing update #52.
After both of these errors plesk version increased and no problem happened.
Now i afraid of installing new update because it may stop working after update....
Ok, looks like I understood the reason. When panel renders status of update installation process, it performs request to the server, and sometimes this request appears in the very same moment, when backend service plesksrv is restarted. Normally, restart of service performed very fast and you shouldn't see any errors. Probably in your environment this procedure lasts a bit longer, and panel requests status of update in that moment.
Please don't worry and consider this problem as an issue in UI representation of update status, this is not critical.
Thank you for reporting this issue.