Closed Shadex9 closed 1 month ago
@qdm12 is more or less the only maintainer of this project and works on it in his free time. Please:
I'm sure this isn't the comment you were hoping or expecting to see, but I just had to let you know that I've been tearing my hair out over the past 24 hours trying to troubleshoot this same error (also using ProtonVPN btw and also on a NAS (asustor), could be relevant) but as I'm new to all things docker so I expected that I was doing something wrong as I've never spun up a gluetun container before!
I'm so happy right now, using v3.38 is indeed working! You've saved the day for me tbh.
I am having this same issue! Also ruining on a synology nas.
This should be fixed by ef6874fe57500ec322469af4d6781e7e4a9e0719 let me know. Related to #2256
I can confirm it is working again. @qdm12 Thanks for the quick fix much appreciated.
Closed issues are NOT monitored, so commenting here is likely to be not seen. If you think this is still unresolved and have more information to bring, please create another issue.
This is an automated comment setup because @qdm12 is the sole maintainer of this project which became too popular to monitor issues closed.
Is this urgent?
Yes
Host OS
Synology DSM6.2
CPU arch
x86_64
VPN service provider
ProtonVPN
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2024-05-02T16:57:20.083Z (commit fb145d6)
What's the problem 🤔
When attempting to start the container it errors out and auto shuts down. This problem occured this morning after updating. Rollback to V3.38 does make it work again.
Share your logs (at least 10 lines)
Share your configuration