OPNsense Forum
Archive => 18.1 Legacy Series => Topic started by: c0mputernick on March 08, 2018, 04:37:25 pm
-
Hello,
I have a strange problem.
Ive installed the latest 8.1.3 release on dedicated hardware for a new firewall that im going to replace pfsense with.
Its not in production yet.
I get random timeouts when i apply settings, like enabling services like IDS or Web proxy, or like this latest one just installing my own SSL cert.
I can ssh into the box and ping out just fine, but the GUI gives me a timeout even whey i refresh. Ive tried other browsers, incognito mode etc. Even tried reloading all services from the CLI and it didnt have any effect. Ive tried rebooting the box as well, i can still ssh to it, but the GUI will not load, just times out.
This has happened every time i try to get this box setup. At first i thought i was trying to do too much at once, so i reset everything back to factory default and just setup my aliases, dns overrides and port forwards and everything seemed fine. I went and imported my SSL cert, choose it in the general settings and when i hit reload it just times out.
Ive tried rebooting the box as well, i can still ssh to it, but the GUI will not load, just times out.
Ive searched the forum and didnt see anything related to the issues im having, is there anything you guys can think of that i can try to resolve this or am i looking at another reset to factory? In the past it has eventually come back up on its own, like if i have 2 tabs open, one will still work while the other times out. Weird stuff. So far this hasnt happened, the GUI is not coming back up.
Id really like to use this software but so far its not been that stable for me, ive tried virtual and physical boxes. Kinda makes me worried about putting this into production. Any help would be greatly appreciated.
-
Since you're applying your own X.509 certificate, I take it you're using the host name to access OPNsense?
Where is the DNS hosted? Have you tried a hosts entry to exclude name resolution?
See if you can capture the problem with a packet trace, either on your client or on the firewall. Wireshark will tell you where the time-outs occur.
Needless to say this behaviour is entirely atypical.
Bart...
-
Do you maybe use HAproxy for connecting to your UI?
EDIT: sorry @franco
-
Please don't ask people to do something they have not said they installed in the first place. "HAProxy" search comes up empty for me here.
Cheers,
Franco
-
Try changing the GUI port to, lets say, 82 and make sure you have the anti-lockout enabled.
Test it on HTTP before you use HTTPS.
See if it works using an IP such as http://192.168.1.1:82. That would tell you if you have a DNS issue.