Re: Firewall blocking my new Debian 11 server ports 80 and 443

Subject: Re: Firewall blocking my new Debian 11 server ports 80 and 443

From: Tom Browder <tom.browder@gmail.com>

Date: Wed, 1 Jun 2022 12:15:56 -0500

Message-id: <[🔎] CAFMGiz-9Ft1WTDus+pLxZu5VPeKrF7VRXen7b83Pi=L9ZiP1UA@mail.gmail.com>

In-reply-to: <[🔎] 34e3778c-f8d7-f616-80bb-469c077ec43f@mail.com>

References: <CAFMGiz-+QnsVVbfxR+fsjXsvSSnU3=C_P1=iasvdHO6SwmC0Xw@mail.gmail.com> <CAHv=rM3EUybtB1+fGCDG6bFapkvYqpbRNrLfxvHTaTZ12DzFqg@mail.gmail.com> <CAFMGiz-OyFC=oJfpg5rZiJnKjNrinEBqOUU2FDGkrXeHpjrcYg@mail.gmail.com> <4451c2f0-1164-bf57-81fe-38c4d98f1e06@mail.com> <YpPHtN+SeqmKwHaX@wooledge.org> <CAFMGiz88oN2YjHdqfz-OCoX5QM46mmOYZjQt3ce63mmeNf3-LA@mail.gmail.com> <YpPdhcq3d96ej9+c@wooledge.org> <CAFMGiz8cxne4sXXDcsA4WqwKWO6bUwDcFvp6=3Hb=S7MBbtLcw@mail.gmail.com> <a8e9bc58-9924-b5aa-c1bc-d21a0f1ad8d4@mail.com> <CAFMGiz9MQtjPwbovkyesYTGkP-fU8F6sGKYGWDsHJFKuRj6KVg@mail.gmail.com> <YpTJe3ICajpuB0q8@wooledge.org> <e8e98cb4-f5a5-c2e0-d969-3d730c54edc7@plainemail.net> <[🔎] CAFMGiz8MJYOaLnZ5QNhaCxeo20RtKbYH=Bnyk0Yj6Cq7FDAydg@mail.gmail.com> <[🔎] 34e3778c-f8d7-f616-80bb-469c077ec43f@mail.com>

On Wed, Jun 1, 2022 at 11:21 john doe <johndoe65534@mail.com> wrote:

> when does it actually start operating? Does it do so then, or does it take

> a reboot?

Apparently, if you 'enable' 'ufw', it will start and be enabled at boot.

Good, thanks.

According to (1), ufw should work with nftables, I did not follow the
reasoning on why to use iptables but only if you have issues use legacy
iptables.

Well, the guidance I got was varying. In my mind, Il Ka seemed to be the most well-informed and understanding of my specific needs, and I went with his recommendations. He was upfront about why he stayed with iptables, and I also favor that view. Based on my experience upgrading Debian since version 4, I know I don't like to jump on new stuff right away, but expect to have to eventually.

-Tom

Reply to: