• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Plesk Firewall Import create double entries

NormanHuth

New Pleskian
Server operating system version
Debian 12.4
Plesk version and microupdate number
18.0.58 #2
I have an entry like this in the export:
JSON:
    {
        "name": "Allow Incoming Database Connections",
        "direction": "input",
        "action": "allow",
        "ports": "3306/tcp",
        "from": "XX.XXX.XXX.XXX",
        "class": "custom",
        "type": "custom",
        "originalId": 231,
        "id": 281
    },

I am changing this position. I have tested the 4 possibilities:

JSON:
    {
        "name": "Allow Incoming Database Connections",
        "direction": "input",
        "action": "allow",
        "ports": "3306/tcp",
        "from": "YY.YYYY.YYYY.YYY",
        "class": "custom",
        "type": "custom",
        "originalId": 231,
        "id": 281
    },

or

JSON:
    {
        "name": "Allow Incoming Database Connections",
        "direction": "input",
        "action": "allow",
        "ports": "3306/tcp",
        "from": "YY.YYYY.YYYY.YYY",
        "class": "custom",
        "type": "custom",
        "originalId": 281
    },

or

JSON:
    {
        "name": "Allow Incoming Database Connections",
        "direction": "input",
        "action": "allow",
        "ports": "3306/tcp",
        "from": "YY.YYYY.YYYY.YYY",
        "class": "custom",
        "type": "custom"
    },

or

JSON:
    {
        "name": "Allow Incoming Database Connections",
        "direction": "input",
        "action": "allow",
        "ports": "3306/tcp",
        "from": "YY.YYYY.YYYY.YYY",
        "class": "custom",
        "type": "custom",
        "originalId": 231
    },

No matter how. After the plesk ext firewall --import command I always have the entry with the XXX & YYY value in the firewall. So the second value is simply added and the old one is kept.

I have also checked the import file. As intended, the XXX entry is not present in this file.
 
So. I no longer need Premium Support in the forum.

I have found a solution that works for men.

You can also simply update the rules, delete them, etc., such as
Code:
plesk ext firewall --set-rule -from={ip} -id={id}

So you can build your own firewall script.

All options are available as usual with help:
Code:
plesk ext firewall --help
 
Back
Top