When adding LAN OPNSense Web GUI unreachable after addding it

Started by clnutter1984, December 01, 2022, 04:33:07 PM

Previous topic - Next topic
I would not use the Wizard on first login. Simply abort it by pressing on the logo. Set your WAN to static manually, leave the LAN untouched (as it is apparently working, otherwise no GUI, or?) and see what happenz next...

kind regards
chemlud
____
"The price of reliability is the pursuit of the utmost simplicity."
C.A.R. Hoare

felix eichhorns premium katzenfutter mit der extraportion energie

A router is not a switch - A router is not a switch - A router is not a switch - A rou....

Quote from: cookiemonster on December 02, 2022, 06:02:16 PM
Yes it does.
And you are connecting to the appliance how during and after physical installation?
I wonder if you have your machine needing to renew the dhcp lease as it might have a different from the old assignment?

On Console,  It prompts for WAN first. Then  Connected indicates UP do the config  Then LAN connected indicates UP the do the config

At this point the Web GUI becomes unreachable.   Leaving only console with keyboard as root.

FYI When booting it gives no errors for hardware same with when I did the fresh install.

Quote from: chemlud on December 02, 2022, 06:08:35 PM
I would not use the Wizard on first login. Simply abort it by pressing on the logo. Set your WAN to static manually, leave the LAN untouched (as it is apparently working, otherwise no GUI, or?) and see what happenz next...

OK, to be clear. I have tried console to setup. Web GUI will not connect even though it indicated as loaded. When both WAN and LAN as configured.

I tried the wizard AND if the WAN and LAN are configured the Web GUI will not connect even though it was Just working. IE on reload of the page or saving the changes.

Doing it with out the wizard via the Web GUI works fine until WAN and LAn are configured and again will not connect. 

IF I leave just LAN configured I can connect via the LAN side to the Web GUI.  Not problem but as soon as I bring up the WAN side and save it fails to connect. 

I have to be missing something easy or stupid.  I admit this is my first time out with OPNsense.


Right so you are still conneceted via the console to the same ip as the UI. Sorry I missed that before.
Surely is not that you are connecting with http instead of https and you've tried both, right?
What message do you get on the web-browser exactly?

Quote from: cookiemonster on December 02, 2022, 07:02:54 PM
Right so you are still conneceted via the console to the same ip as the UI. Sorry I missed that before.
Surely is not that you are connecting with http instead of https and you've tried both, right?
What message do you get on the web-browser exactly?

This is what I get when it fails to connect. 
Unable to connect

An error occurred during a connection to 192.168.1.1.

    The site could be temporarily unavailable or too busy. Try again in a few moments.
    If you are unable to load any pages, check your computer's network connection.
    If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.

I see. I can only imagine a problem with getting from the pc/laptop to the device if console is OK. Browser Cookies, addons, that sort of thing if the connection is done in the same way ie. same cables, over the same path, etc.
Maybe the browser developer tools (Ctr+Shft+I) gives an indication. Network tab.

Failing that, we're going to have to dive into command lines. Both from client and opn shell. We could use Wireshark.
And I think the UI is lighttpd, so wouldn't hurt to see if the process is running and the log seems to be /var/log/lighttpd/latest.log

please start (again) with a simple setup.
  Connect the first port directly wired to your computer.
  Second connector to WAN.

Follow the steps. It is basically next ...next...next. The WAN should show some "strange" internet IP and the LAN the 192.168.1.1.
Your pc should be able to connect to this IP. If not re-insert the UTP connector to force a DHCP request.

> IT first asks to configure WAN.  Then LAN.  If I configure WAN first I can access the Web GUI.   

Also noticed some remarks about accessing GUI on the WAN/Internet? This will not work. How is your cabling? Because your WAN should be one cable to your ISP (modem). So, you can not use this "strange" internet IP to access the GUI. You have to use 192.168.1.1.

Also noticed something about renaming OPT1 to LAN? Why are you doing this?