Search results

It specifically says in the help: --remove-rules or -d <rule_id_1>[,<rule_id_2>[,...]] So, don't use -id... just --remove-rules ID

Does it? I sure hope it's a smooth transition upon release... it would not be pleasant if we all had to use Plesk migrator to move to a whole new server using Stream once it's released...

Disable must be for the firewall as a whole. Gotta run help on the firewall command to see what options it provides for removing a rule.

Yeah, it should be. Large number; you go through a lot of rules? You can remove the `-Ne` part to see the DB structure.

Run this to get your list of rules: plesk db -Ne 'select id,object from module_firewall_rules where configuration_id=2' Grab the ID from that for your rule. I don't have the exact command to delete or disable it, but it looks something like this: plesk bin modules/firewall/settings --disable -id...

When we run a re-sync with Plesk migrator to refresh the data at the destination, prior to 'flipping the switch' over to the new server, for every 5 subscriptions it does this for about 3-4 minutes: Overall - Fetch configuration data from Plesk servers Presumably it's grabbing info on the...

Yep, we do the same. In terms of copying settings, we built a standardization script that uses Plesk CLI and DB updates to configure each server exactly as we like it. That saves a huge chunk of time, though it definitely took a while to build. We use Plesk Migrator for the data transfer. Then...

Yes exactly. At least the conversion seems straightforward as packages probably don't differ significantly at this time: CentOS Stream root@centos-linux# dnf install centos-release-stream root@centos-linux# dnf distro-sync root@centos-stream# cat /etc/centos-release CentOS Stream release 8...

Yep, same issue here. Plesk devs will need to fix this in the installer, but as a workaround, I modified /etc/yum.repos.d/CentOS-Linux-PowerTools.repo. Change [powertools] to [PowerTools] and you should be all set.

For unknown reasons this doesn't appear to be a problem with apache restarts anymore. I reinstalled Phusion and the apache service appears to be able to stop fine. However nginx is still an issue. If I edit /usr/share/passenger/phusion_passenger/locations.ini and comment out...

This is a weird one. The commands systemctl stop httpd and systemctl stop nginx hang until timeout (90s) on CentOS 8. I narrowed it down to Phusion Passenger -- once removed (via Plesk Installer), nginx and httpd stop normally. When I reinstall Passenger (which I kinda need for nodejs and ruby...

On the OpenVZ bug trakcer, one of the Virtuozzo devs indicated the final fix for this will be included in the kernel released along with Virtuozzo 7.0 Update 15, which is expected to be released at the end of October. Error - bugs.openvz.org Given this info, I'm guessing that the issue was...

There's a comment on an unrelated bug report (seems to have been a glitch) that is referenced in passing as these versions supposedly containing the fixes for this systemd session leakage problem: cat /etc/virtuozzo-release Virtuozzo release 7.0.13 (136) uname -a Linux server.com...

Vz7 around here too. I take it you were running CentOS 7 containers on the Virtuozzo 6 nodes (2.6.32 kernel) prior to migration to Virtuozzo 7? It's quite possible that running CentOS 7 with systemd on kernel 2.6.32 simply handles systemd sessions differently (like a form of backwards...

hmm, that’s handy in its own way, and I suppose does answer the original question. we were looking to generate a plesk admin password that matches all the Plesk requirements. Specifically the set of symbols that are allowed is rather limited. We used the utility apg but had to enter a lot of...

This would be handy!

Thanks Igor! That worked here too: rpm -Uvh http://mirror.centos.org/centos-7/7/os/x86_64/Packages/ImageMagick-6.9.10.68-3.el7.x86_64.rpm --nodeps yum update -y Some Mirrors do not still have those updates.

Still happening here. I'm guessing some mirrors haven't received the updated packages. Will check again tomorrow.

The underlying dbus issue that was pinpointed as the cause of this bug (for most users) was fixed in RedHat and CentOS with a dbus update months ago, yet the workaround cron script in the Plesk Support article you provided are still needed. Has there been any indication as to why this is the...

Same here, but weirdly possibly only on CentOS 6 servers; no such alerts from CentOS 7 servers. I don't think there *was* an original alert of a problem; I think this is some kind of bug in the email notifications...