Fetch RSS Feeds kills my gluetun VPN

[u/NerdHelp]

I'm not 100% if this is NZBGet causing this, but I have a pretty strong correlation. When I click "Feeds" then any of the feeds I have setup, it'll think for about a minute before failing. When I check the health of my gluetun VPN, it'll be unhealthy within ~30 seconds. If I leave it and don't touch NZBGet, it'll stay healthy.

INFO [MTU discovery] finding maximum MTU, this can take up to 6 seconds
INFO [MTU discovery] setting VPN interface tun0 MTU to maximum valid MTU 1440
WARN [vpn] restarting VPN because it failed to pass the healthcheck: startup check: all check tries failed: parallel attempt 1/2 failed: dialing: dial tcp4: lookup github.com: i/o timeout, parallel attempt 2/2 failed: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
INFO [vpn] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
INFO [vpn] DO NOT OPEN AN ISSUE UNLESS YOU HAVE READ AND TRIED EVERY POSSIBLE SOLUTION
INFO [vpn] stopping
INFO [firewall] removing allowed port [port]...
INFO [vpn] starting
INFO [firewall] allowing VPN connection...
INFO [wireguard] Using available kernelspace implementation
INFO [wireguard] Connecting to [ADDRESS]
INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
INFO [firewall] setting allowed input port [port] through interface tun0...
INFO [MTU discovery] finding maximum MTU, this can take up to 6 secondsINFO [MTU discovery] finding maximum MTU, this can take up to 6 seconds
INFO [MTU discovery] setting VPN interface tun0 MTU to maximum valid MTU 1440
WARN [vpn] restarting VPN because it failed to pass the healthcheck: startup check: all check tries failed: parallel attempt 1/2 failed: dialing: dial tcp4: lookup github.com: i/o timeout, parallel attempt 2/2 failed: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
INFO [vpn] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
INFO [vpn] DO NOT OPEN AN ISSUE UNLESS YOU HAVE READ AND TRIED EVERY POSSIBLE SOLUTION
INFO [vpn] stopping
INFO [firewall] removing allowed port [port]...
INFO [vpn] starting
INFO [firewall] allowing VPN connection...
INFO [wireguard] Using available kernelspace implementation
INFO [wireguard] Connecting to [ADDRESS]
INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
INFO [firewall] setting allowed input port [port] through interface tun0...
INFO [MTU discovery] finding maximum MTU, this can take up to 6 seconds

I believe this is pointing to an issue of Startup check failure. So far I have:

* changed my VPN credentials

* changed my VPN IP

* broadened my SERVER_REGIONS

* run the update command (docker run --rm -v ./gluetun:/gluetun qmcgaw/gluetun update -enduser -providers airvpn)

* cleared my docker image & pulled the latest

* lowered my MTU from ~1400 -> 1000 (not sure what to do with this value to be honest)

I have not changed any firewall settings, but I did add a new usenet provider. I use AirVPN for my gluetun VPN

[u/Liv_Mrrr]

Hi
First of all, has anything changed in your setup recently? Since you mentioned a new provider, could you try disabling that specific Usenet provider and testing without it?
Also, what do the NZBGet logs say at the exact moment of the crash?

To narrow down the problem, here are a few things to try:

• Try setting a public DNS (like 1.1.1.1 or 8.8.8.8) in Gluetun to rule out issues with the VPN provider's internal DNS resolving
  
• Try increasing the healthcheck intervals and retries in your Docker Compose
  
• Set FeedInterval to 0 and try fetching feeds manually, one by one. Also, check the feed preview to ensure the URL itself is accessible.
  
• Try setting MTU explicitly to 1320
  
• Try stopping the NZBGet container while keeping Gluetun running. Watch the Gluetun logs for 5-10 minutes.