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 version of linuxserver/wireguard fails to create peer configuration when PEERS is set to string instead of int #54

Open
kostaleonard opened this issue Dec 17, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@kostaleonard
Copy link
Owner

An update to linuxserver/wireguard breaks the VPN because the peer configuration file is not generated correctly. The PEER argument in the bootstrap needs to be changed from a string to an int. Here is a version that works on the EC2 instance:

ubuntu@ip-10-0-1-9:~$ sudo docker run -d   --rm   --name=bulwark   --cap-add=NET_ADMIN   --cap-add=SYS_MODULE   -e PUID=1000   -e PGID=1000   -e TZ=Europe/London   -e PEERS=1   -e SERVERURL=3.139.88.229   -e SERVERPORT=51820   -e INTERNAL_SUBNET=10.13.13.0   -e ALLOWEDIPS=10.0.0.0/8   -e PEERDNS=auto   -p 51820:51820/udp   -v /etc/wireguard:/config   -v /lib/modules:/lib/modules   --sysctl="net.ipv4.conf.all.src_valid_mark=1"   linuxserver/wireguard
11325e5af39a4ae62ddf0c094eae454e71f307ce346de617fb50ba763147656c
ubuntu@ip-10-0-1-9:~$ ls /etc/wireguard
coredns  peer1  server  templates  wg0.conf
ubuntu@ip-10-0-1-9:~$ ls /etc/wireguard/peer1
peer1.conf  peer1.png  presharedkey-peer1  privatekey-peer1  publickey-peer1
@kostaleonard kostaleonard added the bug Something isn't working label Dec 17, 2022
@kostaleonard kostaleonard added this to the Second release milestone Dec 17, 2022
@kostaleonard kostaleonard self-assigned this Dec 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant