-
Hi ! I am totally new to docker and VPN management, sorry in advance if I'm terrible at it. I want to isolate some dockers with my Mullvad VPN and of course with Wireguard, as it seems the new must-have for everyone here. Thanks a lot !! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Yes I saw that too, I believe the key they show in the web ui is the hash digest of the actual private key which is in the configuration file. That bummed me out too 😄
Copy paste the docker run -it --rm --cap-add=NET_ADMIN \
-e VPNSP=mullvad \
-e VPN_TYPE=wireguard \
-e WIREGUARD_ADDRESS="11.48.216.37/32" \
-e WIREGUARD_PRIVATE_KEY="OFf8G73HKurisHXAUmrXxU5C0VD50EMn3N9KAbut/1k=" \
qmcgaw/gluetun Note that with Mullvad, you can use the same address and private key for all servers (which is awesome), so it's really a set once and forget type of environment variables. The server 'public key', endpoint, port and location information are all built in gluetun so no need to set them (they are taken from https://api.mullvad.net/www/relays/all/ and stored in the program here). For Wireguard files support, you can subscribe to #610 although using those two environment variables you set once are most likely much easier to use for Mullvad. A few VPN knowledge points:
A few Docker knowledge points:
Finally, I can share a docker-compose.yml if you want if you can't set it up in Portainer, just let me know! |
Beta Was this translation helpful? Give feedback.
Yes I saw that too, I believe the key they show in the web ui is the hash digest of the actual private key which is in the configuration file. That bummed me out too 😄
Copy paste the
Private Key
andAddress
values from any of the Wireguard configurations you downloaded. You only need to setWIREGUARD_PRIVATE_KEY
andWIREGUARD_ADDRESS
as specified in the Mullvad table. For example: