Skip to content
\n

and I can't access WebUI via 192.168.0.30:51821 which is my server's IP in my LAN. only can access via public domain (and I don't want expose WebUI on WAN, this is only for ddns)

\n

which setting should I edit?
\nsetting I already try:
\nnetwork_mode bridge or host
\nports 51821:51821 or 127.0.0.1:51821:51821

","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"

With this config:
\n - 127.0.0.1:51821:51821
\nIt's expected you would not be able to reach the WebUI at 192.168.0.30 (the binding is done strictly with the host's loopback address).

\n

You should be able to reach it at 192.168.0.30 with this config (binding done with 0.0.0.0):
\n - 51821:51821

\n

What method are you using to forward traffic from the internet to the docker host where wg-easy is running on?
\nWithout that additional info, I can't really tell whether or not this config below would achieve what you want:
\n - 192.168.0.30:51821:51821

\n

Network_mode bridge typically would be sufficient, but using \"bridge\" or \"host\" depends on how you want to expose container ports, which other containers you are running and how you want to isolate them from each other (and on the local network).

\n

Since you did not declare a network explicitly in the compose file, bridge is the mode being employed right now.

","upvoteCount":1,"url":"https://github.com/wg-easy/wg-easy/discussions/1527#discussioncomment-11336100"}}}

Can't access WebUI via 192.168.x.x #1527

Answered by shalafi99
Nebulosa-Cat asked this question in Q&A
Discussion options

You must be logged in to vote

With this config:
- 127.0.0.1:51821:51821
It's expected you would not be able to reach the WebUI at 192.168.0.30 (the binding is done strictly with the host's loopback address).

You should be able to reach it at 192.168.0.30 with this config (binding done with 0.0.0.0):
- 51821:51821

What method are you using to forward traffic from the internet to the docker host where wg-easy is running on?
Without that additional info, I can't really tell whether or not this config below would achieve what you want:
- 192.168.0.30:51821:51821

Network_mode bridge typically would be sufficient, but using "bridge" or "host" depends on how you want to expose container ports, which other containers you a…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Nebulosa-Cat
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants