Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New container with wireguard fails to start #368

Open
c2mfj opened this issue Jun 11, 2023 · 3 comments
Open

New container with wireguard fails to start #368

c2mfj opened this issue Jun 11, 2023 · 3 comments

Comments

@c2mfj
Copy link

c2mfj commented Jun 11, 2023

New container with latest pull with wireguard as vpn client fails to start b/c wireguard conf does not exist. The directions state that I should place the wireguard conf after the first start of the container.

2023-06-11 13:36:29.268817 [info] System information Linux df7f5c8a7a68 5.4.0-150-generic #167-Ubuntu SMP Mon May 15 17:35:05 UTC 2023 x86_64 GNU/Linux
2023-06-11 13:36:29.392883 [info] OS_ARCH defined as 'x86-64'
2023-06-11 13:36:29.501764 [info] PUID defined as '0'
2023-06-11 13:36:29.635152 [info] PGID defined as '0'
2023-06-11 13:36:30.029417 [info] UMASK defined as '000'
2023-06-11 13:36:30.135356 [info] Permissions already set for '/config'
2023-06-11 13:36:30.328222 [info] Deleting files in /tmp (non recursive)...
2023-06-11 13:36:30.477631 [info] VPN_ENABLED defined as 'yes'
2023-06-11 13:36:30.540555 [info] VPN_CLIENT defined as 'wireguard'
2023-06-11 13:36:30.596781 [info] VPN_PROV defined as 'custom'
2023-06-11 13:36:30.962061 [crit] No WireGuard config file located in /config/wireguard/ (conf extension), please download from your VPN provider and then restart this container, exiting...

@MarcS1975
Copy link

same problem here
any solutions?

@binhex
Copy link
Owner

binhex commented Feb 27, 2024

yeah, the solution is in the log:-
No WireGuard config file located in /config/wireguard/ (conf extension), please download from your VPN provider and then restart this container, exiting...

@MarcS1975
Copy link

MarcS1975 commented Feb 27, 2024

Thanks. I did that and now the containers launch but I cannot access the GUI via QB_HOST_IP:8484. This is my Compose. I had to change ports. Does that cause problems?:

version: "2.2"
services:
qbittorrentvpn:
image: binhex/arch-qbittorrentvpn
container_name: binhex-qbittorrentvpn
#wireguard
privileged: true
environment:
- PUID=0
- PGID=0
- TZ=Europe/London
- UMASK=000
- VPN_ENABLED=yes
- VPN_PROV=custom
#- VPN_CLIENT=openvpn
- VPN_CLIENT=wireguard
#- STRICT_PORT_FORWARD=yes
- LAN_NETWORK=MYLAN/24
- NAME_SERVERS=1.1.1.1,1.0.0.1,9.9.9.9
- DEBUG=false
- WEBUI_PORT=8484
- ENABLE_PRIVOXY=no
#- VPN_OPTIONS=additional openvpn cli options
volumes:
- MYPATH/arch-qbittorrentvpn/data:/data
- MYPATH/arch-qbittorrentvpn/config:/config
- /etc/localtime:/etc/localtime:ro
#wireguard
- /lib/modules:/lib/modules:ro
ports:
- 6882:6881
- 6882:6881/udp
- 8484:8080
- 8118:8118
cap_add:
- NET_ADMIN
#wireguard
- SYS_MODULE
#Needed for wireguard
sysctls:
- net.ipv4.conf.all.src_valid_mark=1
restart: unless-stopped

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants