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

To: Edwin Zimmerman <edwin@plainemail.net>

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 06:45:51 -0500

Message-id: <[🔎] CAFMGiz8MJYOaLnZ5QNhaCxeo20RtKbYH=Bnyk0Yj6Cq7FDAydg@mail.gmail.com>

In-reply-to: <e8e98cb4-f5a5-c2e0-d969-3d730c54edc7@plainemail.net>

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>

On Mon, May 30, 2022 at 19:46 Edwin Zimmerman <edwin@plainemail.net> wrote:

On 5/30/22 09:41, Greg Wooledge wrote:
> On Mon, May 30, 2022 at 07:13:54AM -0500, Tom Browder wrote:
>> No worries. All those responses about the subject IP now are the norm for a
>> bare-iron server ready for use by a customer, yours truly. It is the same
>> server I messed up the firewall with and locked myself out of. The OS has
>> been reinstalled and is ready for me to use again.

On that note, for my next try with the server, I will definitely use UFW with the legacy uptables that was suggested.

But a question: it is clear that it must be enabled to go into effect, but when does it actually start operating? Does it do so then, or does it take a reboot?

-Tom

Reply to: