Added Mullvad setup script for Wireguard#1130
Merged
thespad merged 9 commits intolinuxserver:wireguard-mullvadfrom Feb 22, 2026
Merged
Added Mullvad setup script for Wireguard#1130thespad merged 9 commits intolinuxserver:wireguard-mullvadfrom
thespad merged 9 commits intolinuxserver:wireguard-mullvadfrom
Conversation
Signed-off-by: Josh Stark <4211747+JoshStark@users.noreply.github.com>
|
PR build pushed to |
|
PR build pushed to |
thespad
approved these changes
Feb 22, 2026
github-project-automation
bot
moved this from PRs
to PRs Approved
in Issue & PR Tracker
|
PR build pushed to |
thespad
approved these changes
Feb 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
A bash script which provides a simpler experience in setting up a
wg0.conffile when running the Wireguard container in client mode. This specifically interacts with Mullvad's APIs to obtain user and relay information, allowing users to define which node(s) to connect through.Benefits of this PR and context:
The point of this change is to alleviate the need for users to manually manage conf files, also account for any potential server-side changes on Mullvad's end (e.g. removal of nodes or changes to IPs or keys).
How Has This Been Tested?
I've got a copy of the init script running as a setup script on my own instance of wireguard which has been working well.
Source / References: