Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is it normal for upgrade from SFOS 16.05.2 MR2 to SFOS 16.05.2 MR3 to disable admin web interface?

Hi new user here.

Just got the home edition installed as a bridge device, working well until I updated from MR2 to MR3 when the web intefrace was disabled.  Is this normal?  I had to figure out how to re-enable from command line!

I had not removed the web interface from my LAN zone.  It was disabled on all interfaces.

alex



This thread was automatically locked due to age.
  • No, that might imply there is something wrong with your bridge setup. Are you sure you went from 5.2 mr 2 to 5.2 mr3 or did you go to 5.3 mr3?

  • Good to know its not normal, i keep seeing it disable the web acces randomly.

    I have only been using the UI as i hate all things CLI and avoid like the plague.

    These are the only two versions every installed on my hardware. (you are right i got the version number wrong in the heading)

    SFOS 16.05.2 MR-2
     
         
    SFOS 16.05.3 MR-3

     

    thats what i moved between, that's what i have in the firmware ui, i put it back to MR-2, then i had to reenable with 'system appliance access enable' at the CLI.

    Then I upgraded to MR3 a second time and on reboot i had to run the command again, now seems ok.

     

    Wow this seems flaky, i blew away pfsense thinking this would be less flaky option...

     

    Thanks for letting me know i wasn't going mad :-)

  • Do you have an option of adding another NIC to your XG?

    Put that in normal mode to see if that allows you access after an upgrade.

    I suspect you might have a rule which is badly setup causing you to loose access to your web gui. Just a thought.

  • I already have four ports and port 4 i configured as a LAN zone before i did anything (i have done this goat rodeo before with pfsense where i locked myself out due to rules). Port 4 does not participate in the bridge.

     

    This is not a rules issues.

    Rules were set, it worked, it got a reboot it worked, no change made other than apply firmware - bang access went.

    I have just been through 2 more reboots since the process i outlined above (without changing the rules AT ALL) and it now works.

     

    I suspect a non-deterministic / race condition like issue on boot may actually cause this rather than the upgrade itself i have seen it on both firmwares.

     

    I assumed it might be some sort of security response i.e disable web when being attacked? but i guess not?

     

    FWIW this is the hardware https://www.amazon.com/Firewall-Micro-Appliance-Gigabit-Barebone/dp/B01GIVQI3M/ref=sr_1_2?ie=UTF8&qid=1492680212&sr=8-2&keywords=pfsense

  • I use the same device for XG Home and did not have this issue. I just performed the upgrade a few minutes ago. I will report back if I notice the issue but the upgrade seemed to go okay for me.