Closed DiamondPrecisionComputing closed 2 years ago
I also see the same error after upgrading to version pr848 just now. Host: Fedora Server CPU_Arch; x86_64 VPN: ProtonVPN Running docker-compose
Logs:
qbit_gluetun | ========================================
qbit_gluetun | =============== gluetun ================
qbit_gluetun | ========================================
qbit_gluetun | =========== Made with ā¤ļø by ============
qbit_gluetun | ======= https://github.com/qdm12 =======
qbit_gluetun | ========================================
qbit_gluetun | ========================================
qbit_gluetun |
qbit_gluetun | Running version pr-848 built on 2022-02-20T03:27:48.093Z (commit dcba2bb)
qbit_gluetun |
qbit_gluetun | š§ Need help? https://github.com/qdm12/gluetun/discussions/new
qbit_gluetun | š Bug? https://github.com/qdm12/gluetun/issues/new
qbit_gluetun | āØ New feature? https://github.com/qdm12/gluetun/issues/new
qbit_gluetun | ā Discussion? https://github.com/qdm12/gluetun/discussions/new
qbit_gluetun | š» Email? quentin.mcgaw@gmail.com
qbit_gluetun | š° Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
qbit_gluetun | 2022/02/20 08:56:12 INFO routing: default route found: interface eth0, gateway 172.17.0.1
qbit_gluetun | 2022/02/20 08:56:12 INFO routing: local ethernet link found: eth0
qbit_gluetun | 2022/02/20 08:56:12 INFO routing: local ipnet found: 172.17.0.0/16
qbit_gluetun | 2022/02/20 08:56:12 INFO firewall: enabling...
qbit_gluetun | 2022/02/20 08:56:12 INFO firewall: enabled successfully
qbit_gluetun | 2022/02/20 08:56:12 INFO storage: merging by most recent 11173 hardcoded servers and 11173 servers read from /gluetun/servers.json
qbit_gluetun | panic: runtime error: invalid memory address or nil pointer dereference
qbit_gluetun | [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x711a33]
qbit_gluetun |
qbit_gluetun | goroutine 20 [running]:
qbit_gluetun | github.com/qdm12/gluetun/internal/configuration/settings.OpenVPN.validate({{0xc000024070, 0x3}, {0xc00002602d, 0x10}, {0xc00002a011, 0x20}, 0xc00053a3a0, {0x0, 0x0, 0x0}, ...}, ...)
qbit_gluetun | github.com/qdm12/gluetun/internal/configuration/settings/openvpn.go:112 +0x293
qbit_gluetun | github.com/qdm12/gluetun/internal/configuration/settings.(*VPN).validate(_, {0x1, {0x4, 0x614c8660, {0xc0002a6000, 0xb8, 0xb8}}, {0x1, 0x61f2977a, {0xc0000ae000, ...}}, ...})
qbit_gluetun | github.com/qdm12/gluetun/internal/configuration/settings/vpn.go:38 +0x1f8
qbit_gluetun | github.com/qdm12/gluetun/internal/configuration/settings.(*Settings).Validate.func1()
qbit_gluetun | github.com/qdm12/gluetun/internal/configuration/settings/settings.go:45 +0x5f
qbit_gluetun | github.com/qdm12/gluetun/internal/configuration/settings.(*Settings).Validate(_, {0x1, {0x4, 0x614c8660, {0xc0002a6000, 0xb8, 0xb8}}, {0x1, 0x61f2977a, {0xc0000ae000, ...}}, ...})
qbit_gluetun | github.com/qdm12/gluetun/internal/configuration/settings/settings.go:50 +0x990
qbit_gluetun | main._main({0xd2ad98, 0xc0000ac040}, {{0xd17408, 0x6}, {0xd176e8, 0x7}, {0xd19220, 0x18}}, {0xc00001e210, 0x1, ...}, ...)
qbit_gluetun | ./main.go:226 +0xca5
qbit_gluetun | main.main.func1()
qbit_gluetun | ./main.go:87 +0x150
qbit_gluetun | created by main.main
qbit_gluetun | ./main.go:86 +0x649```
I'm also see the same error after upgrading to version pr-848. Host: Debian Bullseye CPU_Arch; x86_64 VPN: Surfshark Running docker-compose
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x711a33]
goroutine 50 [running]:
github.com/qdm12/gluetun/internal/configuration/settings.OpenVPN.validate({{0xc0000240a0, 0x3}, {0xc00002800d, 0x18}, {0xc00002a011, 0xa}, 0xc00001efc0, {0x0, 0x0, 0x0}, ...}, ...)
github.com/qdm12/gluetun/internal/configuration/settings/openvpn.go:112 +0x293
github.com/qdm12/gluetun/internal/configuration/settings.(*VPN).validate(_, {0x1, {0x4, 0x614c8660, {0xc00028c000, 0xb8, 0xb8}}, {0x1, 0x61f2977a, {0xc0001a6000, ...}}, ...})
github.com/qdm12/gluetun/internal/configuration/settings/vpn.go:38 +0x1f8
github.com/qdm12/gluetun/internal/configuration/settings.(*Settings).Validate.func1()
github.com/qdm12/gluetun/internal/configuration/settings/settings.go:45 +0x5f
github.com/qdm12/gluetun/internal/configuration/settings.(*Settings).Validate(_, {0x1, {0x4, 0x614c8660, {0xc00028c000, 0xb8, 0xb8}}, {0x1, 0x61f2977a, {0xc0001a6000, ...}}, ...})
github.com/qdm12/gluetun/internal/configuration/settings/settings.go:50 +0x990
main._main({0xd2ad98, 0xc000494000}, {{0xd17408, 0x6}, {0xd176e8, 0x7}, {0xd19220, 0x18}}, {0xc00001e210, 0x1, ...}, ...)
./main.go:226 +0xca5
main.main.func1()
./main.go:87 +0x150
created by main.main
./main.go:86 +0x649
something went wrong with last commit? =)
Last working version for me
docker pull qmcgaw/gluetun:v3.27.0
Same error after upgrading to version 3.28.0 from 3.27.0 Host: Ubuntu 20.04 Arch: amd64 Running with docker-compose
What a Sunday morning wake up! š
It looks like I have some CI tagging/pushing spaghetti mix-up, pr-848
is from https://github.com/qdm12/gluetun/pull/848
Anyway I manually pushed the latest image so it works again, and will fix up the build pipeline.
Let's leave this opened until I fix the build pipeline. Anyway I need to rework it to do another release tag like today š
Build pipeline fixed! š
You can also now use image :v3
which corresponds to the latest v3 release, if you prefer stability over the edge.
Update (Resolution): Well, that's strange... but I updated my Compose from image: qmcgaw/gluetun:latest to image: qmcgaw/gluetun:v3.37.0 and the Gluetun container is healthy now
Why would this same issue from 2022 suddenly affect me? "panic: runtime error: invalid memory address or nil pointer dereference"
I've been running the latest version (v3.37.0) for several months and everything was fine. But it broke today. I tried removing the container and setting it up again, but the same error results.
Ubuntu Server 22.04.4 with latest updates/upgrades VPN: Proton Docker Compose
@egadgetboy Funny enough, ran into the same problem just now - thank you for recommending to use v3.37.0....don't know why we were getting those problems...
Running into the same problem now also... wth?
yea.. for some reason, what egadgetboy suggested works, updated compose with specific version and it worked.
Ditto... latest update causes issue #855. Rollback to v3.37.0 fixed.
Since v3.37.0 is the latest release, not sure if this is the issue (as in... which version is being pulled when using :latest) but I noticed that this page shows the latest version is an older version 3.35.0: https://github.com/qdm12/gluetun-wiki
Same issue occurred here, fixed with changing the tag to v3.37 in compose.
Ugh, had the same issue today. Due to the fact that I added another container to my docker-compose file, I assumed I had corrupted something that way. Now it seems more likely that it pulled the latest gluetun at the same time and caused the error. Specifying v3.37.0 fixed the issue.
Same thing here. Thanks for the workaround. Must remember to switch back at some point in future :-)
To the many people who commented today, please note this issue is completely irrelevant to #2169 - it's just the panic: runtime error: invalid memory address or nil pointer dereference
message which is the same, but this is a Go (programming language) builtin common error, when trying to access a nil pointer.
Is this urgent?
Yes
Host OS
unRAID
CPU arch
x86_64
VPN service provider
Private Internet Access
What are you using to run the container
Other
What is the version of Gluetun
pr-848
What's the problem š¤
Container constantly restarts do to error after merging servers.json. Reverted back to "vpnsecure.me" tag does not yield the same error.
Share your logs
Share your configuration