-
Notifications
You must be signed in to change notification settings - Fork 112
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
Comments
same problem here |
yeah, the solution is in the log:- |
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?:
|
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...
The text was updated successfully, but these errors were encountered: