{"id":233648,"is_content":1,"post_type":"post","post_title":"ERROR: problem running ufw-init","slug":"error-problem-running-ufw-init","source_value":"https:\/\/askubuntu.com\/questions\/585430\/error-problem-running-ufw-init","fake_user_id":86870,"published_at":"2021-12-02T11:28:05.000000Z","view_count":0,"deleted_at":null,"created_at":"2022-02-09T08:36:13.000000Z","updated_at":"2023-04-29T16:10:23.000000Z","content":[{"id":11071499,"post_id":233648,"fake_user_id":23966,"content_dec":"
\n \n

I tried setting up ufw<\/code> on my remote Ubuntu 14.04 server so i installed it and allowed ssh<\/code> with the command <\/p>\n\n

sudo ufw allow ssh\n<\/code><\/pre>\n\n
after that I tried to enable ufw<\/code> but I get the following error:<\/p>\n\n
ERROR: problem running ufw-init\niptables-restore: line 77 failed\niptables-restore: line 30 failed\niptables-restore: line 10 failed\niptables-restore: line 39 failed\niptables-restore v1.4.21: Couldn't load target `ufw-user-input':No such file or directory\n\nError occurred at line: 2\nTry `iptables-restore -h' or 'iptables-restore --help' for more information.\n\nProblem running '\/etc\/ufw\/before.rules'\nProblem running '\/etc\/ufw\/after.rules'\nProblem running '\/lib\/ufw\/user.rules'\n<\/code><\/pre>\n\n
Then I found this<\/a> troubleshooting guid which recommends to comment some lines in the mentioned .rules files, but I would have to comment every line in all the files to get it starting. I can't do that since I need at least the allow ssh<\/code> rule.<\/p>\n\n
The most suspicious line is the one mentioning a iptables-restore<\/code> error:<\/p>\n\n
iptables-restore v1.4.21: Couldn't load target `ufw-user-input':No such file or directory\nError occurred at line: 2\nTry `iptables-restore -h' or 'iptables-restore --help' for more information.\n<\/code><\/pre>\n\n
The in the error mentioned .rules files are as following now:<\/p>\n\n
before.rules:<\/p>\n\n
# rules.before\n#\n# Rules that should be run before the ufw command line added rules. Custom\n# rules should be added to one of these chains:\n#   ufw-before-input\n#   ufw-before-output\n#   ufw-before-forward\n#\n\n# Don't delete these required lines, otherwise there will be errors\n*filter\n:ufw-before-input - [0:0]\n:ufw-before-output - [0:0]\n:ufw-before-forward - [0:0]\n:ufw-not-local - [0:0]\n# End required lines\n\n\n# allow all on loopback\n-A ufw-before-input -i lo -j ACCEPT\n-A ufw-before-output -o lo -j ACCEPT\n\n# quickly process packets for which we already have a connection\n-A ufw-before-input -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT\n-A ufw-before-output -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT\n-A ufw-before-forward -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT\n\n# drop INVALID packets (logs these in loglevel medium and higher)\n-A ufw-before-input -m conntrack --ctstate INVALID -j ufw-logging-deny\n-A ufw-before-input -m conntrack --ctstate INVALID -j DROP\n\n # ok icmp codes for INPUT\n-A ufw-before-input -p icmp --icmp-type destination-unreachable -j ACCEPT\n-A ufw-before-input -p icmp --icmp-type source-quench -j ACCEPT\n-A ufw-before-input -p icmp --icmp-type time-exceeded -j ACCEPT\n-A ufw-before-input -p icmp --icmp-type parameter-problem -j ACCEPT\n-A ufw-before-input -p icmp --icmp-type echo-request -j ACCEPT\n\n# ok icmp code for FORWARD\n-A ufw-before-forward -p icmp --icmp-type destination-unreachable -j ACCEPT\n-A ufw-before-forward -p icmp --icmp-type source-quench -j ACCEPT\n-A ufw-before-forward -p icmp --icmp-type time-exceeded -j ACCEPT\n-A ufw-before-forward -p icmp --icmp-type parameter-problem -j ACCEPT\n-A ufw-before-forward -p icmp --icmp-type echo-request -j ACCEPT\n\n# allow dhcp client to work\n-A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT\n\n#\n# ufw-not-local\n#\n-A ufw-before-input -j ufw-not-local\n\n# if LOCAL, RETURN\n#-A ufw-not-local -m addrtype --dst-type LOCAL -j RETURN\n\n# if MULTICAST, RETURN\n#-A ufw-not-local -m addrtype --dst-type MULTICAST -j RETURN\n\n# if BROADCAST, RETURN\n#-A ufw-not-local -m addrtype --dst-type BROADCAST -j RETURN\n\n# all other non-local packets are dropped\n-A ufw-not-local -m limit --limit 3\/min --limit-burst 10 -j ufw-logging-deny\n-A ufw-not-local -j DROP\n\n# allow MULTICAST mDNS for service discovery (be sure the MULTICAST line above\n# is uncommented)\n#-A ufw-before-input -p udp -d 224.0.0.251 --dport 5353 -j ACCEPT\n\n# allow MULTICAST UPnP for service discovery (be sure the MULTICAST line above\n# is uncommented)\n#-A ufw-before-input -p udp -d 239.255.255.250 --dport 1900 -j ACCEPT\n\n# don't delete the 'COMMIT' line or these rules won't be processed\nCOMMIT\n<\/code><\/pre>\n\n
after.rules:<\/p>\n\n
# rules.input-after\n#\n# Rules that should be run after the ufw command line added rules. Custom\n# rules should be added to one of these chains:\n#   ufw-after-input\n#   ufw-after-output\n#   ufw-after-forward\n#\n\n# Don't delete these required lines, otherwise there will be errors\n*filter\n:ufw-after-input - [0:0]\n:ufw-after-output - [0:0]\n:ufw-after-forward - [0:0]\n# End required lines\n\n# don't log noisy services by default\n-A ufw-after-input -p udp --dport 137 -j ufw-skip-to-policy-input\n-A ufw-after-input -p udp --dport 138 -j ufw-skip-to-policy-input\n-A ufw-after-input -p tcp --dport 139 -j ufw-skip-to-policy-input\n-A ufw-after-input -p tcp --dport 445 -j ufw-skip-to-policy-input\n-A ufw-after-input -p udp --dport 67 -j ufw-skip-to-policy-input\n-A ufw-after-input -p udp --dport 68 -j ufw-skip-to-policy-input\n\n# don't log noisy broadcast\n#-A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input\n\n# don't delete the 'COMMIT' line or these rules won't be processed\nCOMMIT\n<\/code><\/pre>\n\n
user.rules:<\/p>\n\n
*filter\n:ufw-user-input - [0:0]\n:ufw-user-output - [0:0]\n:ufw-user-forward - [0:0]\n:ufw-before-logging-input - [0:0]\n:ufw-before-logging-output - [0:0]\n:ufw-before-logging-forward - [0:0]\n:ufw-user-logging-input - [0:0]\n:ufw-user-logging-output - [0:0]\n:ufw-user-logging-forward - [0:0]\n:ufw-after-logging-input - [0:0]\n:ufw-after-logging-output - [0:0]\n:ufw-after-logging-forward - [0:0]\n:ufw-logging-deny - [0:0]\n:ufw-logging-allow - [0:0]\n:ufw-user-limit - [0:0]\n:ufw-user-limit-accept - [0:0]\n### RULES ###\n\n### tuple ### allow any 22 0.0.0.0\/0 any 0.0.0.0\/0 in\n-A ufw-user-input -p tcp --dport 22 -j ACCEPT\n-A ufw-user-input -p udp --dport 22 -j ACCEPT\n\n### END RULES ###\n\n### LOGGING ###\n-A ufw-after-logging-input -j LOG --log-prefix \"[UFW BLOCK] \" -m limit --limit 3\/min --limit-burst 10\n-A ufw-after-logging-forward -j LOG --log-prefix \"[UFW BLOCK] \" -m limit --limit 3\/min --limit-burst 10\n-I ufw-logging-deny -m conntrack --ctstate INVALID -j RETURN -m limit --limit 3\/min --limit-burst 10\n-A ufw-logging-deny -j LOG --log-prefix \"[UFW BLOCK] \" -m limit --limit 3\/min --limit-burst 10\n-A ufw-logging-allow -j LOG --log-prefix \"[UFW ALLOW] \" -m limit --limit 3\/min --limit-burst 10\n### END LOGGING ###\n\n### RATE LIMITING ###\n-A ufw-user-limit -m limit --limit 3\/minute -j LOG --log-prefix \"[UFW LIMIT BLOCK] \"\n-A ufw-user-limit -j REJECT\n-A ufw-user-limit-accept -j ACCEPT\n### END RATE LIMITING ###\nCOMMIT\n<\/code><\/pre>\n\n
Does anyone have had similar issues and solved it or has any idea how to solve the problem(s)?<\/p>\n\n
Thanks in advance.<\/p>\n    <\/div>","created_at":"2023-06-09T21:52:05.000000Z","updated_at":"2023-06-09T21:52:05.000000Z"},{"id":11071500,"post_id":233648,"fake_user_id":69949,"content_dec":"

\n
There is a \/usr\/share\/ufw\/check-requirements<\/code> script that checks for everything needed for ufw<\/code> to work. You'll get hints about what's missing.<\/p>\n\n
ufw<\/code> is not meant to work without the full iptables\/netfilter<\/code> build in the kernel or loaded by modules. If you can't build a new kernel, you're in for some trouble.<\/p>\n\n
The post you linked tries to go around these problems. They also say the ufw application scripts still don't work. You could try port 22 instead of ssh<\/code>.<\/p>\n    <\/div>","created_at":"2023-06-09T21:52:05.000000Z","updated_at":"2023-06-09T21:52:05.000000Z"}],"tags":[{"id":184,"slug":"14-04","name":"14.04","suggest":0,"count":20082,"tag_group_id":null,"description":null},{"id":43,"slug":"server","name":"Server","suggest":0,"count":14703,"tag_group_id":null,"description":null},{"id":341,"slug":"firewall","name":"Firewall","suggest":0,"count":1091,"tag_group_id":null,"description":null},{"id":668,"slug":"iptables","name":"Iptables","suggest":0,"count":1172,"tag_group_id":null,"description":null},{"id":346,"slug":"ufw","name":"Ufw","suggest":0,"count":634,"tag_group_id":null,"description":null}],"tagged":[{"id":679467,"taggable_id":233648,"taggable_type":"App\\Models\\Post","tag_name":"14.04","tag_slug":"14-04","tag":{"id":184,"slug":"14-04","name":"14.04","suggest":0,"count":20082,"tag_group_id":null,"description":null}},{"id":679468,"taggable_id":233648,"taggable_type":"App\\Models\\Post","tag_name":"Server","tag_slug":"server","tag":{"id":43,"slug":"server","name":"Server","suggest":0,"count":14703,"tag_group_id":null,"description":null}},{"id":679469,"taggable_id":233648,"taggable_type":"App\\Models\\Post","tag_name":"Firewall","tag_slug":"firewall","tag":{"id":341,"slug":"firewall","name":"Firewall","suggest":0,"count":1091,"tag_group_id":null,"description":null}},{"id":679470,"taggable_id":233648,"taggable_type":"App\\Models\\Post","tag_name":"Iptables","tag_slug":"iptables","tag":{"id":668,"slug":"iptables","name":"Iptables","suggest":0,"count":1172,"tag_group_id":null,"description":null}},{"id":679471,"taggable_id":233648,"taggable_type":"App\\Models\\Post","tag_name":"Ufw","tag_slug":"ufw","tag":{"id":346,"slug":"ufw","name":"Ufw","suggest":0,"count":634,"tag_group_id":null,"description":null}}]}