• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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