You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I'm having an issue setting this up. I can access the webui just fine via localhost:port if I am using bridge networking, but the second I try to spin up a container with host networking (required for my use-case), my browser refuses to connect to the webUI.
This is the console output. With host networking, I get a bunch of random IPv6 addresses that I have no clue where they're from.
Host networking
Bridge networking:
I'm not sure what is going on here. I can't access the webui via loopback or server's ip address with host networking.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
So I'm having an issue setting this up. I can access the webui just fine via localhost:port if I am using bridge networking, but the second I try to spin up a container with host networking (required for my use-case), my browser refuses to connect to the webUI.
This is the console output. With host networking, I get a bunch of random IPv6 addresses that I have no clue where they're from.
Host networking
Bridge networking:
I'm not sure what is going on here. I can't access the webui via loopback or server's ip address with host networking.
Beta Was this translation helpful? Give feedback.
All reactions