My port 443 can't be reached

User @Leavii has been update to basic user (Trust Level 1).

2 Likes

TY TY TY

1 Like

Thank you! Going back :smiley:

3 Likes

OK the NAT seems correct.
Now onto the firewall rules.
Show and tell :slight_smile:

Still said I had to wait 22 hours so I will stay on this one for now. I also didn't have the Disco bot message on that account as I do on this one. So firewall rules...

1 Like

Here we are..

How does anything get in at all?

Is there a quick-start guide or something for that router?

To me, it seems like line one is just the opposite of line two.

  1. Allow things in state
  2. Drop thing not in state

That works great for outbound I guess.
But how does anything inbound pass initially to get into state????

Here are my routes. I have a NetOnix that powers APs, etc... but I am direct into the ER with this host. Not sure what you are needing, but I can reach the site and the others all fine and never have had any issues with anything going in or out.

Your other user shouldn't have those replies limitation now, maybe you should logout and login to activate the changes but no problem using your new user but take care or you will reach the replies limitation again.

1 Like

I will log out and in again to test. Thanks!

This is NOT a routing problem.
It's an accessibility problem.
Can you add a rule that says:

Source *
Dest {your outside IP}
Protocol {HTTPS or TCP 443}
Action accept

I have it bridged to the internal DHCP scope.

Yeah I will give it a shot.

So it there a separate router and firewall?

Can you hit the site locally?
curl -Iki https://192.168.1.87/

[from the server itself]

No just this one firewall for the host. Before the firewall is the modum.

curl -Iki https://192.168.1.87 returns:

@linux00:~$ curl -Iki https://192.168.1.87/
HTTP/1.1 301 Moved Permanently
Date: Sun, 24 Jan 2021 19:59:33 GMT
Server: Apache/2.4.41 (Ubuntu)
X-Redirect-By: WordPress
Location: https://jackiesmcs.com/
Content-Type: text/html; charset=UTF-8
1 Like

OK so the modem is in bridge mode.
Then the firewall is what you have been showing.
I think we need that rule there [in the firewall].

What choices/options does it show for "protocol" ?

The modem is not in bridge mode just passes the public IP. The bridge interface is to 192.168.1.1/24.

Protocol options:

Under Protocol by name there is not an HTTP or HTTPS option.

After logging out and back in it says I still have 21 hours to wait.

My WAN goes to ETH0 from the modem.

What happens when you chose "TCP" ?

What happens when you chose "Choose a protocol by name" ?