• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Question psa-firewall via cli/ansible

Dave W

Regular Pleskian
Hi all,

To enable and confirm the firewall via CLI it has to be done from different sessions otherwise you get:
"Applying and confirmation of firewall changes should be done via different ssh sessions."

Is there any way to disable this?
Dave
 
Hi all,

To enable and confirm the firewall via CLI it has to be done from different sessions otherwise you get:
"Applying and confirmation of firewall changes should be done via different ssh sessions."

Is there any way to disable this?
Dave


Hi Dave, you found a solution for that?

I have the same issue.


Thanks!
 
Hi VGS,
My solution was to disable plesk-firewall and just create my own iptables ruleset and use that with Ansible.

# Disable the Plesk firewall extension
- name: Disable Plesk Firewall
command: /usr/local/psa/bin/modules/firewall/settings -d removes=/etc/rc.d/init.d/psa-firewall
# Remove the Plesk firewall extension if installed
- name: UnInstall Plesk Firewall Extension if installed
command: plesk installer --select-release-current --remove-component psa-firewall removes=/etc/rc.d/init.d/psa-firewall

# Upload the the iptables file and restart iptables
- name: Upload the the iptables file to /etc/sysconfig/ and restart iptables
copy: src=files/security/iptables dest=/etc/sysconfig owner=root group=root mode=0644 backup=yes
notify:
- restart iptables

Not really a fix but it works for me.
Dave
 
Hi Dave,

Thanks for your answer. Yesterday I found a tricky solution for this problem using firewall system from Plesk. I prefer using that because we have created a auto-deploy system for Plesk containers in our infrastructure and we need to use the same features that users can.

First, you need to have SSH enabled with SSH Key allowed for root. You can do it uncommenting "#PermitRootLogin prohibit-password" in /etc/ssh/sshd_config

Then, you can do something like that:
  1. Generate local SSH Pub key: ssh-keygen -t rsa -f /root/.ssh/id_rsa -P ''
  2. Copy your local pub key to local allowed keys: cat /root/.ssh/id_rsa.pub > /root/.ssh/authorized_keys
  3. Enable firewall: /usr/local/psa/bin/modules/firewall/settings -e
  4. Confirm the changes by this way: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p XXX root@localhost '/usr/local/psa/bin/modules/firewall/settings -c'
  5. Optional, clean your local authorized_key: echo '' > /root/.ssh/authorized_keys

I hope this can help someone.

Regards!
 
Back
Top