Search results

Wait. Seriously, don't ever use ch.origin.autoinstall.plesk.com as installation source. It is slow. It is acceptable to use it only for mirroring.

This is for Plesk Installer only, i.e. for downloading system packages. AFAIK, Extension Catalog packages do not support downloading over proxy. But you could probably set up some transparent proxy by doing some iptables magic. I'm not going to provide specific instructions here.

plesk installer has the following relevant options (from --help-options): Download options: --source <URL or absolute path> Installation source: a mirror URL or an absolute path to a directory containing top-level products.inf3 file...

Just make sure /lib/x86_64-linux-gnu/libm.so.6 and /lib/x86_64-linux-gnu/libc.so.6 are up-to-date in your chroot environments.

This is resolved with the latest update of SSH Terminal.

This is resolved with the latest update of SSH Terminal.

xmlrpc extension is no longer available (upstream discontinued its support). ionCube loader extension is not available yet (no version compatible with PHP 8). imagick extension is not available yet (no version compatible with PHP 8).

Moreover, many popular applications do not work on PHP 8 yet.

Check the article Igor posted above. If the last symptom is not present, this might be a previously unknown issue, in which case you're advised to address Plesk support.

Run full plesk repair mail to fix.

To update to the latest Obsidian you may run: plesk installer upgrade plesk release To install the latest update in scope of the same 3-digit version: plesk installer update Updating to next versions on unsupported OSes (such as Debian 8, which has reached EOL) is unsurprisingly not possible.

Sorry, but no. If you wish to have a customized phpMyAdmin installation (including any supported PHP version), you are free to install it manually on a domain. However, among other things you'll loose functionality of automatic login from Plesk.

The issue happens only on very specific setups (e.g. with specific Docker images running), so looks like it should be relatively rare. The workaround will be automatically reverted on the next update, so no extra actions should be needed.

Your target server uses Debian 8, which is not supported by Plesk anymore (so no new versions). See also Feature Deprecation Plan I suggest using a more modern OS supported by Plesk, such as Debian 10 or 9.

Unless you have a VM snapshot you can revert to, there is no way. Plesk doesn't support downgrade.

FYI: the issue is confirmed as PPPM-12387 and will be fixed in 18.0.31. Until then, if you're affected, it is sufficient to use the provided workaround.

This is expected. Is the issue still present for you after applying the workaround?

It's slightly weird that a restart was required. Anyway, the message means that your phpMyAdmin installation now operates without configuration storage (settings will not be saved on server side, only in your cookies), unless you've already addressed this somehow. The message explains why this...

Yes, it's possible since Plesk Obsidian.

Those that had a problem and restarting sw-cp-server service helped, could you post your OS, please? Did you have any errors or warnings on update to 18.0.30 (at least in /var/log/plesk/install/autoinstaller3.log)?