Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
Anti-lockout rule not updating on port change?
« previous
next »
Print
Pages: [
1
]
Author
Topic: Anti-lockout rule not updating on port change? (Read 1052 times)
BrianDiPalma
Newbie
Posts: 2
Karma: 0
Anti-lockout rule not updating on port change?
«
on:
March 09, 2022, 11:38:12 pm »
I wanted to expose a local web server to the internet so I changed OPNsense's port to 440 yet once changed I couldn't access the web GUI. I sshed in and reverted the port change.
Does the anti-lockout rule not update to take into account web GUI port changes? I can add a new rule myself but I'm just surprised that I was locked out.
Logged
cookiemonster
Hero Member
Posts: 1817
Karma: 94
Re: Anti-lockout rule not updating on port change?
«
Reply #1 on:
March 10, 2022, 11:18:19 am »
I didn't get locked out when I changed to custom port in the past. Maybe I needed to clear browser cache or something similar, can't remember.
"I couldn't access the web GUI" is not clear enough. Did you get to it but got an http response code, which one? Did you not get to it? Needs clarification.
Logged
BrianDiPalma
Newbie
Posts: 2
Karma: 0
Re: Anti-lockout rule not updating on port change?
«
Reply #2 on:
March 10, 2022, 03:04:04 pm »
I tried it again and it worked. Really weird. I noticed that the custom port input behaved oddly last night when it failed. I couldn't click select all of it or get my cursor placed at the end of the "443" value. I had to delete all of it and replace it with "440". This time the input worked as I'd expect. Well it works that's all that matters.
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
Anti-lockout rule not updating on port change?