O omexlu Regular Pleskian Apr 3, 2017 #1 Hello, on last Plesk update i had an error on panel that the update has not been done completly, here LetsEncrypt was not updated, where can i find the error message again? And how try to reupdate the plugin? Thanks.
Hello, on last Plesk update i had an error on panel that the update has not been done completly, here LetsEncrypt was not updated, where can i find the error message again? And how try to reupdate the plugin? Thanks.
U UFHH01 Guest Apr 3, 2017 #2 Hi omexlu, omexlu said: where can i find the error message again? Click to expand... You will find the install - logs at "/var/log/plesk/install" omexlu said: And how try to reupdate the plugin? Click to expand... Did you consider to go to: HOME > Extensions > Updates or/and did you use the command: Code: plesk installer --select-product-id plesk --select-release-current --upgrade-installed-components or/and plesk installer --select-product-id plesk --select-release-current --reinstall-patch --install-component base
Hi omexlu, omexlu said: where can i find the error message again? Click to expand... You will find the install - logs at "/var/log/plesk/install" omexlu said: And how try to reupdate the plugin? Click to expand... Did you consider to go to: HOME > Extensions > Updates or/and did you use the command: Code: plesk installer --select-product-id plesk --select-release-current --upgrade-installed-components or/and plesk installer --select-product-id plesk --select-release-current --reinstall-patch --install-component base
O omexlu Regular Pleskian Apr 3, 2017 #3 Hello, Here is the errormessage from the update for letsencrypy: Extension package ext-letsencrypt 2.0.1-24 install$ stderr: Unable to open source file. Not zip file. Click to expand... Running the update manually from panel solved the problem. Last edited: Apr 3, 2017
Hello, Here is the errormessage from the update for letsencrypy: Extension package ext-letsencrypt 2.0.1-24 install$ stderr: Unable to open source file. Not zip file. Click to expand... Running the update manually from panel solved the problem.