Search results

There's quite a few system firewall implementations out there. Plesk Firewall extension works only with iptables or those that provide compatibility layer for iptables (such as nft). Other implementations (such as firewalld) should be turned off before enabling Plesk Firewall.

Firewall 2.0.2 was released. It includes a number of improvements to address activation issues you've encountered. See also its changelog for instructions on increasing confirmation timeout in case simple extension update will not resolve the issue in your case. The root cause in each...

To the original posters: Firewall 2.0.2 was released. It includes a number of improvements to address activation issues you've encountered. See also its changelog for instructions on increasing confirmation timeout in case simple extension update will not resolve the issue in your case. CLI...

Applying firewall configuration should be an interactive operation. Otherwise one risks completely cutting off access to the server for the user. After adding your customizations show a notification in Plesk that suggests the user to go to the Firewall page, review the rules, and apply the...

@danami, I'm sure other Plesk devs already communicated this to the Warden devs, but I'll duplicate this information here, just in case. This is an internal utility. Nobody should use it directly or pay attention to whatever is written in its help, except for the Firewall extension developers...

Please update to the latest Plesk 18.0.40.

Fix for the issue has been released. Please update your Plesk (e.g. via plesk installer update).

Of course, there are cases when package system must be temporarily broken to achieve the needed result. Plesk packages removal is generally not one of them.

Please don't use --nodeps or even rpm for removal. This way you don't guarantee package system consistency. Just use yum remove instead and review other packages (if any) that would be removed.

You may remove the package as long as Plesk Installer reports Dovecot is in use (rather than Courier-IMAP).

Did you perform a dist-upgrade from Debian 8 recently? What's your output of apt-cache policy systemd? Make sure systemd package is upgraded. See also the KB.

In general you should likely have more log messages detailing the error. You may also want to make sure that port 8447 isn't occupied before starting Plesk Installer from UI. As a workaround, you may install the update in console mode by running plesk installer via SSH.

Well, I assume there's no cgroups tree mounted at /sys/fs/cgroup (see mount | grep cgroup) on Windows. That's most likely the issue in your case. The image will not work without it.

Please make sure you're using the correct and full docker run command from the image description. Don't use plesk/plesk:tests — it is obsolete and is not maintained anymore.

That's not a good way at all. The proper way is to just remove the extension from UI (as advised above) or via plesk bin extension -u ssh-terminal if you or your clients don't need it.

Yes, it's new. It's useful only if your server obtains any of its IP addresses via DHCP (i.e. serves as DHCP client).

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.