V18.5 MR2: https://community.sophos.com/sophos-xg-firewall/b/blog/posts/sophos-firewall-v18-5-mr2-is-now-available
Release V18.5 MR1 Post (326): https://community.sophos.com/sophos-xg-firewall/b/blog/posts/sophos-firewall-v18-5-mr1-is-now-available
EAP(318) Blog Post: https://community.sophos.com/sophos-xg-firewall/b/blog/posts/sophos-firewall-v185-mr1-eap
"Old" MR3 Thread: https://community.sophos.com/xg-firewall/f/discussions/123403/xg-firewall-v18-mr-3-feedback-and-experiences
"Old" MR4 Thread: https://community.sophos.com/sophos-xg-firewall/f/discussions/124771/xg-firewall-v18-mr-4-feedback-and-experiences
"Old" MR5 Thread: https://community.sophos.com/sophos-xg-firewall/f/discussions/127053/xg-firewall-v18-mr-5-feedback-and-experiences
Any chance AES-NI support for SW installs made it into this update? Believe its Jira ID NC-59127.
Running in HA, upgraded and both nodes got up OK with new version, now I get "Only administrator can access the auxiliary device" when logging into the "primary" node.... Internet works, so not critical, can try to reboot or swap the nodes, but any suggestions before that?
Sophos XGA 2100 @ Home | Sophos v19 Architect
Seems like the HA is not up2date right now and take some time. The Webadmin will take some more time to get up.
No I actually found the cause!
Creating a in-cognito browser session, allows me to login, so a cokkie session of some sort?! :-)
Using the "old" browser windows still gives the above warning, closing and reopening browser solves it.