Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

sevo

Members
  • Joined

  • Last visited

  1. Resolved my issue by limiting maximum active connections, it was unlimited.
  2. It's a strange issue. It seems to be only with ProtonVPN that this is happening. If I use an alternative VPN provider (e.g. PIA with openvpn) it works fine and as expected. But with the ProtonVPN, I repeatedly get satisfactory start ups with torrents downloading and seeding, but then it will start to do the DNS checks and then it fails and stops. The only logs I can ever see are these: 2026-01-18 20:15:23,983 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.140.103 142.250.140.147 142.250.140.99 142.250.140.104 142.250.140.106 142.250.140.105' 2026-01-18 20:15:23,983 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2026-01-18 20:15:23,991 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2026-01-18 20:15:24,000 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 6890 [debug] Deluge incoming port is 6890 [debug] VPN IP is 10.2.0.2 [debug] Deluge IP is 10.2.0.2 2026-01-18 20:15:54,005 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-01-18 20:16:39,059 DEBG 'watchdog-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 11 retries left Might anyone know if there are some other logs I can check to see what exactly is happening when the failure starts? I am still inclined to think this is a ProtonVPN issue but I would expect it to have been resolved by now.
  3. To be honest I'm not sure how to access firewall logs. My ISP's router software is shit and doesn't really have anything helpful in there. Here are the full logs: https://paste.passtheheadphones.me/?2452b4a7fd9df0fb#6zDdpN112G5N5jbvaegqVDrDvYvTKBxvHsCuirbSxiP8
  4. It's sporadic, sometimes it works on first try sometimes it doesn't. I find if I change the wireguard config to another one (i.e. different server) it will work for a short time then stop working. I have just tried an openvpn alternative and it works for a short time then stops also. I have those name servers set and is also not working.
  5. I don't use any of those :( I can't figure out why this is happening.
  6. I've just recently started having recurring issues with binhex-delugevpn stopping to work. I'm not sure how to debug this any further. It will work for a short time then stop working (ProtonVPN wireguard), see logs: 2026-01-17 21:04:39,111 DEBG 'start-script' stdout output: [debug] ProtonVPN assigned incoming port is '55114' 2026-01-17 21:05:04,976 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-01-17 21:05:35,013 DEBG 'watchdog-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 11 retries left 2026-01-17 21:06:10,051 DEBG 'watchdog-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 10 retries left 2026-01-17 21:06:45,091 DEBG 'watchdog-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 9 retries left 2026-01-17 21:07:05,237 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.129.105 142.250.129.106 142.250.129.147 142.250.129.99 142.250.129.103 142.250.129.104' Now it has completely failed and won't pass the retry. I have tried changing my wg config to a different server and again, it works briefly then stops working. Can anyone please help me debug this? I haven't changed anything, it has worked flawlessly for months. I note this: 2026-01-17 21:14:00,734 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.