• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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