feat(container): update image qmcgaw/gluetun ( v3.40.3 → v3.41.0 ) #2733
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.
This PR contains the following updates:
v3.40.3->v3.41.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
qdm12/gluetun (qmcgaw/gluetun)
v3.41.0Compare Source
Video of me reading out this release
Thank you all for your patience for this release which took its sweet time 🙏⏲️
I have been rather absent in a good part of 2025 due to work and life getting in the way, and I would like to thank many of you for helping out around in issues and discussions, and for the few code contributors whilst I was away.
On this release, many of the features you see are the result of behind-the-scene work of the last few years (notably on dns) and I'm super glad they are finally in Gluetun! A lot more to come in v3.42.0, there is already a pile of pull requests waiting 🚀
Final note, introducing the RANTING SECTION at the bottom of this changelog. This section might also be in the future releases (unfortunately)!
Happy holidays! 🎄 🎅 ❄️ ⛄
Features
DNS_UPSTREAM_RESOLVER_TYPEbelow)DNS_UPSTREAM_RESOLVER_TYPEoption which can bedot(DNS over TLS),doh(DNS over HTTPS) orplain(plaintext over UDP)DNS_REBINDING_PROTECTION_EXEMPT_HOSTNAMESi/o timeouterrors are now logged at the debug level instead of warn levelHEALTH_TARGET_ADDRESSESwith a timeout of 6 secondsHEALTH_TARGET_ADDRESSES, with up to 3 tries of 10s, 15s, and 30s timeoutsHEALTH_ICMP_TARGET_IPS, with a fallback to plain DNS (UDP) lookups ofgithub.comto cloudflare+google, with up to 10 tries of 5s, 5s, 5s, 10s, 10s, 10s, 15s, 15s, 15s, and 30s timeoutsHEALTH_TARGET_ADDRESSES=cloudflare.com:443,github.com:443to have a fallback addressHEALTH_ICMP_TARGET_IPS=1.1.1.1,8.8.8.8to have8.8.8.8as a fallback addressHEALTH_SMALL_CHECK_TYPEwhich can bednsoricmp. By default it uses icmp and falls back to dns if icmp isn't permitted.HEALTH_RESTART_VPN: you should really leave it toon, unless you have trust issues with the healthcheck.HTTP_CONTROL_SERVER_AUTH_DEFAULT_ROLEoption (JSON encoded). For example:{"auth":"basic","username":"me","password":"pass"}or{"auth":"apiKey","apikey":"xyz"}or{"auth":"none"}.{{PORT}}template variable on top of{{PORTS}}{{VPN_INTERFACE}}template variable which is by defaulttun0WIREGUARD_ENDPOINT_IP, mention it must be an IP address for the time beingFixes
WIREGUARD_ENDPOINT_IPregression (v3.39.0) fixed to override the IP address of a picked connectionUPDATER_PROTONVPN_EMAILandUPDATER_PROTONVPN_PASSWORD-proton-emailand-proton-passwordflags/v1/openvpn/portforwardedto/v1/portforward: this route has nothing to do with openvpn specifically, removed theedinportforwardedto accomodate future routes such as changing the state of port forwardingPUBLICIP_ENABLEDis now respectedRefererheader (#3058)openvpnconfigcommand no longer panics due to missingSetDefaultscallDNS_KEEP_NAMESERVERbehavior (by the way, you should no longer need to use this option!)Documentation
Maintenance
DOTtoDNS_SERVERDOT_PROVIDERStoDNS_UPSTREAM_RESOLVERSDOT_PRIVATE_ADDRESStoDNS_PRIVATE_ADDRESSESDOT_CACHINGtoDNS_CACHINGDOT_IPV6toDNS_UPSTREAM_IPV6DOT_PRIVATE_ADDRESSsplit intoDNS_BLOCK_IPSandDNS_BLOCK_IP_PREFIXESUNBLOCKwithDNS_UNBLOCK_HOSTNAMESDNS_BLOCK_IP_PREFIXESvalues since DNS rebinding protection is built-in the filter middlewareopenvpn*tovpn*variablesinternal/storage:internal/publicip/api/ip2location: rename countries to match standard country names from the mappingconstants.CountryCodes()`git remote addtaskThe ranting section
🥀 this is a new section in which I'll share my rant among various Gluetun-related things 🌻 💁 expect a lot of uppercasing, heavy punctuation and no structure whatsoever. Enjoy the read ❗
ALPINE!!! STOP BREAKING IPTABLES ON EVERY TWO RELEASES! When I enter
iptables -nL,-nmeans NUMERIC! Then why the hell did0becomeallon Alpine 3.22??!!!?!Gluetun was configured like clockwork to parse these numeric values, and all hell broke lose on some systems where it would return TEXTUAL values!
💁
2e2e5f9and6712adffor more informationPUREVPN did change everything for OpenVPN: certificates, keys, CAs. Like, can't you keep the previous ones working instead of breaking everyone? No-one was really warned on this as far as I know, so obviously Gluetun started failing more and more with PureVPN. Thanks to @mlapaj for patching this and notifying me.
SlickVPN: Ok fine you're going bankrupt or something, but I spent hours programming code to scrape your locations webpage for you to just add some ugly-ass text directly to list your mere 11 servers left? Couldn't you update the table on your website, which, by the way, is still there below, but empty!!? What the heck!? I ended up throwing all my code and just hardcoding their silly
1129 servers in Gluetun, because I'm not spending more hours fixing this scrapper, this is ridiculous.https://www.slickvpn.com/locations/
Ok I'm not going to write the url here but it's
h**ps://gluetun.com. It's an AI generated bullshlt website from some Pakistani idiot in the UK, trying to advertise for themselves to sell "website development" (=AI prompts). I did reach out to them telling them to please shut it down, no answer obviously. I suppose I should trademark gluetun... At least, since it's fully AI-generated, it's almost decent information and there is a bit of honesty in there, like "Not affiliated with Gluetun" at the bottom, although it also says "We at Gluetun" 😄And keeping the best for last: PROTON!... Ah Proton... Proton Proton Proton...
First of all, let's start with Proton blocking their VPN servers data behind a login wall.
There is no reason for this. None. Zip. Zero. Nada.
You can literally connect to a VPN server with a free account.
And anyone with a paid account, including me, could just get that list and share it.
Absolute non-sense of a choice.
But, fine, let's see what's next...
I exchange with other Gluetun users trying to debug how to access this list, how to login programmatically to get that stupid list.
We all throw our keyboards at our monitor out of frustration because Proton's login system is an overly complex thing.
I decide to contact Proton support.
Ah, Proton "support"...
It's like subconsciously they want their users to run away.
I opened a support ticket explaining the situation, very politely of course, and simply asking for a tiny bit of guidance on helping out with the
curlcommands necessary to login and obtain a valid token.Their answer? Polite "go away leave us alone" message:
WHAT SECURITY REASONS!??? You are making a fool of yourselves Proton!
DO YOU THINK I AM STUPID PROTON!??? AND THANKS FOR BEING SO HELPFUL YOU BUNCH OF 10-NEURONS SUPPORT!
You sweet sweet summer child... Really, are you pretending to be a child now? PROTONNNNNN you are just an embarassment to the tech scene.
Yeah thanks for nothing and not even budging a tiny bit on anything.
I even then told them I would tell my users to avoid Proton like the plague because of this ridiculous behavior.
The answer? Basically same thing, reworded.
Guess what?
Well we figured out your authentication (#2878), you unhelpful spineless wonders, so have fun blocking your own users from using your own VPN servers data...
But wait.... this is not even over; A few days later, a Gluetun user notices paid servers are not part of the Gluetun servers data.
Because Proton decided to hide away paid servers data from free users. Mind blown 🤯 This is absolutely stupid to its finest extent.
Anyway, I signed in with a paid account, re-updated the servers data. Done. Now your list is public. Congratulations Proton for your security measures, completely useless.
In conclusion... Proton is unhelpful and takes security decisions that make absolutely no sense.
Please migrate away from Proton whenever you can.
v3.40.4Compare Source
Fixes
DOT=offandDNS_KEEP_NAMESERVER=offWIREGUARD_ENDPOINT_IPoverrides the IP address correctly (regression introduced in v3.39.0)N / AConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.