You are not logged in.
I just updated my server, which has privoxy, nextcloud, apache, and avahi running on it and until now ran without issue. Super simple, after all. Now, every device that uses it is being refused.
On the server itself, everything is running fine. No unusual errors anywhere. I'm guess it's from the iptables update and/or nftables install. Something new is happening and now my server is refusing connections through all its major ports via services, such as avahi-daemon, web server, etc.
How do I diagnose this?
Any help would be greatly appreciated.
Last edited by haigioli (2026-04-06 13:58:09)
Offline
Turns out nftables has a default config that only opens port 22 and ignores all others. The solution was to learn how to add ports in nftables.conf by reading Arch Wiki.
The problem is that such upgrades get slipped in under the radar, leaving us to play detective for a while. Not the first time this has happened; it definitely won't be the last.
I will credit archlinux.org for putting this at the top of 'Latest News'. It's the manner of the rollout that needs some improvement. I looked for messaging in /var/log/pacman.log and saw no message to reflect the enormity of what this upgrade's effects.
Anyway, nftables looks promising, the way that pipewire and wayland did. Like those, it'll take some time to completely replace iptables, but I like what I see, so far.
I'm marking this as SOLVED now.
Offline