August 3, 20223 yr Reason: I would prefer to restrict access to the unRAID webUI to only one of my Ethernet adapters and use ports 80 and 443 on the other adapters for hosting docker applications. Previously i was using the hidden BIND_MGT setting to restrict the WebUI to eth0. However it appears that functionality has been removed in 6.10 per the latest in the discussion here I would like to request a new mechanism, preferably not hidden this time, to support this use case.
August 3, 20223 yr 1 hour ago, itimpi said: I thought the GUI already only worked on eth0? No - its also working over eth1 (in my case)
August 22, 20223 yr +1 for this; one of several things (some of which are admittedly self-inflicted lol) keeping me from heading to 6.10. My eth0 is a shared IPMI/host onboard, and I don't use it for anything other than IPMI as it's 1Gb and vlan'd off at the switch level anyway, instead accessing everything over eth1's 10Gb interface.
March 4, 20233 yr Author So i finally updated my main server to 6.11.5 and having forgot about this ran straight into an issue. Have there been any changes that would allow me to prevent the webui from binding to eth1? @bonienl
May 30, 20251 yr I would also like to keep a interface free from the webui so i can host a dockered reverse proxy on port 80 and 443
April 8Apr 8 https://unraid.net/blog/6-12-0-stableNetwork ImprovementsWe added a new section under Settings->Network Settings->Interface Extra, allowing users to define which interfaces the Unraid services use. By default, all standard interfaces with an IP address are included in the list of listening interfaces.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.