add support for AzireVPN#3223
Conversation
40f126b to
44d5104
Compare
|
@qdm12 would be great to get some feedback on this one! |
|
Hi @jkaberg I've tried out this PR on my setup, and while it seems to set up a VPN correctly, the port forwarding doesn't seem to be working for me: To confirm I'm setting this up correctly, I went to the "VPN" tab in my AzireVPN account, and clicked on "Configuration File" to generate a new configuration file, which was the name of an animal. Inside this was a lot of .conf files, all with the same PrivateKey and Address lines. I copied the PrivateKey value to the WIREGUARD_PRIVATE_KEY env variable, and the IPv4 part ("x.y.z.a/32") to WIREGUARD_ADDRESSES in my docker-compose.yml file. VPN_SERVICE_PROVIDER is set to "azirevpn", and VPN_TYPE to "wireguard". I set SERVER_COUNTRIES to the name of the country I want my traffic to go through, VPN_PORT_FORWARDING to "on", and then I set AZIREVPN_TOKEN to the value which appeared in AzireVPN's Settings->Tokens page after I downloaded that config file. Am I doing something wrong? Thanks! |
|
Not entirely sure why it wouldnt work, here's an snippet of my docker compose environment: Ran a test with above just now and Gluetun logs: |
Yeah, here's mine: Then I get this in the start-up log: But I've also found something odd: if I change the setting for "VPN_PORT_FORWARDING" to "off" and restart, I get this: |
Description
added support for AzireVPN, including support for port forwarding. Support for OpenVPN was not added, more information here
documentation/wiki PR also submitted at qdm12/gluetun-wiki#186
Changes to
servers.jsonare generated withgo run main.go update -maintainer -providers azirevpnIssue
#497
Assertions