DE

↑ ↓ select, Enter open, Esc close

Open a port with nftables

caution rootFirewalldebian, ubuntu

Caution: This command changes the system. Understand what it does before you run it.

Adjust the values, the command updates live
root@server
nft insert rule inet filter input tcp dport 443 accept

Inserts the rule at the top of the input chain in the inet filter table, which is defined in the Debian template /etc/nftables.conf. Using insert instead of add places the rule before any drop rules. The rule applies immediately, but only until a reboot or until nftables.service is reloaded.

Note: The rule only becomes permanent with an entry in /etc/nftables.conf. If the table does not exist, nft reports No such file or directory.

Open question before approval: Prüfen, ob auf Plesk-Servern mit Firewall-Erweiterung die Tabelle inet filter existiert oder die Plesk-Regeln nur in ip filter liegen.

Also searched as

  • nftables open port
  • nft allow tcp port
  • nft insert rule accept

Related one-liners

All in Firewall

Create an IP blocklist set in nftables

#nft add set inet filter blocklist '{ type ipv4_addr; flags interval; }' && nft insert rule inet filter input ip saddr @blocklist drop
cautionFirewall

Show the complete nftables ruleset with handles

#nft -a list ruleset
harmlessFirewall

Add an IP address to an nftables blocklist

#nft add element inet filter blocklist '{ 203.0.113.25 }'
cautionFirewall

Close a port in ufw by deleting its rule

#ufw delete allow 8080/tcp
cautionFirewall

Open a port with ufw

#ufw allow 443/tcp
cautionFirewall

Allow a port only from a specific IP with ufw

#ufw allow from 198.51.100.0/24 to any port 22 proto tcp
cautionFirewall

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.