Open nextcloudfan opened 3 months ago
@nextcloudfan thank you very much
Oui, l'image fournit dans docker compose ne fonctionne pas, l'interface reste inaccessible, j'utilise celle-ci qui fonctionne : linuxserver/wireguard:v1.0.20210914-ls6
Not working with:
Linuxserver.io version: 1.0.20210914-r4-ls52
wireguard | Build-date: 2024-09-19T11:23:35+00:00
I am not sure but i think i have the same issue here with the latest image. it can only be accessed through ipv6 address of the host machine. eg [ipv6adress]:5000
as a workaround i set network_mode: host and ports:
as i think it is like this by design you cannot set host to listen on 0.0.0.0 by default it works only on 127.0.0.1:5000 and you are supposed to setup an http proxy to expose the service.
Linuxserver.io has a section in their readme abou this. You'll need to have below post up and predown in your config to allow access.
https://github.com/linuxserver/docker-wireguard?tab=readme-ov-file#maintaining-local-access-to-attached-services Maintaining local access to attached services ** Note: This is not a supported configuration by Linuxserver.io - use at your own risk.
When routing via Wireguard from another container using the service option in docker, you might lose access to the containers webUI locally. To avoid this, exclude the docker subnet from being routed via Wireguard by modifying your wg0.conf like so (modifying the subnets as you require):
[Interface]
PrivateKey =
With the latest linuxserver wiregaurd image it is not possible the the WG UI. See here: https://forum.openmediavault.org/index.php?thread/50500-if-you-are-experiencing-difficulties-connecting-to-the-wireguard-ui-or-encounter/
You have to use an old image of linuxserver wireguard. When do you plan to update wireguard UI to handle this?