Recent content by zerfl

That's good news, thank you! I suppose checking for updates does not work as intended on my server then. Plesk did not inform me on new available updates, despite auto-checking for updates until I manually pressed "Check for updates". Regardless, thanks again.

While that's true, I think the core issue is that an extension update was pushed that was incompatible with Ubuntu 18.04 / Plesk 18.0.52.3, effectively breaking Plesk UI access. The extension update should not have been released for this Plesk version (or should've been skipped / ignored) in the...

They messed up, I guess it happens. After you make the aforementioned change to the file, you should be able to access to Plesk again. Go ahead and check for extension updates in the UI. For me it was the Docker extension that caused this issue, not the LetsEncrypt extension that was mentioned...

Are there any plans to support translation updates in the future? We're currently using Smart Updates (and loving it!) for nearly 70 WordPress websites and would love to have plugin/theme/core translations updates as well.

If someone has any idea how to further debug this, I would appreciate it.

Too late to edit my op: Additional info: /var/log/plesk/panel.log shows: [2023-03-24 09:46:18.110] 2944074:641d63592d5a1 ERR [panel] Table is not detected after each deploy attempt, but that's about it - no other messages. node@power:~$ ls -l /var/www/vhosts/example.com/ total 36...

Hello, I am not sure how to further debug this so I came here for some help. I have a subdomain, sub.example.com that runs a Laravel application which is connected to a remote git repository. The deployment of files does not work (e.g. moving the new contents to...

The same is true for me as well. Unfortunately, I can not observe any performance improvement in the latest update. Load time on the System tab (Default filter; Today) is 45.01 s. Mail takes 24.21 s. (Mail): Switching from Today to Yesterday: 24.48 s. (System) Switching from Today to...

Hi, Plesk will add a little piece of configuration to your nginx configuration for your domain when setting up Docker Proxy Rules. The docker extension is, quite frankly, very limited in this regard and will always proxy your request to http://0.0.0.0:<port>. When you're accessing your domain...