My gluetun VPN keeps failing the health check after running for a few hours. I found that some had fixed this by changing the update period to a shorter interval, and this worked for a while for me as well. But for the last 24h or so, it keeps failing after a few hours.

How can i fix this?

docker compose:

gluetun log:

  • lemmyvore@feddit.nlEnglish
    0·
    2 months ago

    If all else fails you can overwrite the healthcheck command or even disable it altogether.

      • lemmyvore@feddit.nlEnglish
        0·
        2 months ago

        Wouldn’t you want to turn it off if it doesn’t work reliably? I struggle to see the point of keeping around a health check that behaves erratically.

        • gravitas_deficiency@sh.itjust.worksEnglish
          0·
          2 months ago

          I suppose it’s a personal choice of where you set the bar for your systems.

          Personally, as a software engineer who’s designed and built a lot of systems over the course of my career: nope - not if you want to just set it and forget it, that is. Which I do. And yes, most of the systems I’ve built professionally aren’t to that standard (mostly due to time constraints), which has consistently frustrated me, but you gotta be a little bit zen about stuff you don’t have complete ownership over.

          Maybe your tolerance for manual intervention is lower than mine, but in terms personal standards, I don’t consider a system to be “done” until it’s configured to to handle itself resiliently and recoverably in all but the most catastrophic situations (I.e. basically, a hardware fault, or some sort of fairly serious upstream infrastructure failure).

          All that said: YMMV. It’s a personal preference, and I know my standards would be considered abnormally strict by some.

  • catloaf@lemm.eeEnglish
    0·
    2 months ago

    Have you read and tried each possible solution it tells you about?

      • catloaf@lemm.eeEnglish
        0·
        2 months ago

        Then I would continue following its advice and open an issue. It could be a bug in the program.

        • ExcessShiv@lemmy.dbzer0.comOPEnglish
          0·
          2 months ago

          I’m not very competent with docker, so honestly I think the error is more on my end than theirs. I bet there is some setting I have set incorrectly and I’m just missing it.

  • AnEilifintChorcra@sopuli.xyzEnglish
    0·
    2 months ago

    Are you seeding a lot of torrents?

    Something similar kept happening to me last year, constantly disconnecting no matter what I tried. I thought it was a gluetun issue so I stopped using docker and tried the official ProtonVPN app, openvpn, wireguard and community version of protonvpn, I tried switching from arch to ubuntu on my NAS and the same thing kept happening.

    I was convinced it was a hardware issue so I tried different hardware, same issues.

    The only thing that fixed it was reducing the number of torrents I had seeding. At the time I had ~500 and once I lowered it, I stopped disconnecting.

    Now I run 3 gluetun containers with 1 qbittorrent container connected to each and they each have ~400 torrents seeding and I haven’t had any issues since.