SOLVED -- Can't Access the GUI after wizard reloads

[JW1990Qwerty]

I am building an OPNsense router for my work, and I keep running into a peculiar issue.

When I run through the wizard the normal way, the website will reload, and when I try to return to the web gui (via its new IP address, 192.168.1.1), it will give me the "site cannot be reached" error.  I am able to continue my configurations via SSH, but it would be much more helpful and convenient if I had access to the GUI.  Are there any ideas as to why this is happening?  Thanks in advance for your help!

[JW1990Qwerty]

Bump

[franco]

You don't give any info as to what you are trying to configure so it's impossible to follow and thus no responses assuming it is likely a configuration mistake.

Under normal circumstances the wizard will not cause this.


Cheers,
Franco

[JW1990Qwerty]

My apologies.  We are installing OPNsense on a Protectli.  The Protectli will be used as a router for our customers at our VOIP services company. 

As I said, whenever I go through the wizard as normal, and assign an IP address, I cannot load up the web interface via that IP.

With respect to the protectli,  I believe I have everything connected properly, and have assigned and connected the cables and interfaces properly.

(Lan is igb1, Wan is igb0--does this sound correct?)

Has anyone had any issues with protectli similar to this?

[JW1990Qwerty]

We have a static IP from the ISP.  Should I be setting up LAN to be provided an IP via DHCP?  The test bench I have at my work is fairly jumbled, and I am also trying to figure out how to get it online.

[koushun]

My guess is that whenever you use the wizard, the interfaces switch; your LAN is no longer the LAN, it is the WAN. What you think is your WAN is no longer the WAN, it has become your LAN interface.

Default for OPNsense, if I remember correctly, is to define the first available interface as the LAN.

Set a static IP adress within the same network range as the firewalls LAN address on a client. Detach all cables and try to do a simple ping test on each port available on your protectcli.

When you've got a reply, you have found your LAN interface and can continue your adventure :)

[franco]

Wait, are we talking about the "wizard" wizard of the GUI (does not flip interfaces) or the "wizardy" console/ssh assignment options 1 & 2?

Again, details matter.


Cheers,
Franco

[JW1990Qwerty]

My guess is that whenever you use the wizard, the interfaces switch; your LAN is no longer the LAN, it is the WAN. What you think is your WAN is no longer the WAN, it has become your LAN interface.

Default for OPNsense, if I remember correctly, is to define the first available interface as the LAN.

Set a static IP adress within the same network range as the firewalls LAN address on a client. Detach all cables and try to do a simple ping test on each port available on your protectcli.

When you've got a reply, you have found your LAN interface and can continue your adventure :)

That's exactly what I did and it is now working.  Thanks!

[koushun]

Great!

Please read the forum rules, and mark this post as [SOLVED]

:)

[JW1990Qwerty]

Thanks