goose_ws

I'm also experiencing this. My `sabnzbd.error.log` shows: Traceback (most recent call last): File "/usr/lib/sabnzbd/SABnzbd.py", line 1786, in <module> main() File "/usr/lib/sabnzbd/SABnzbd.py", line 1238, in main publicipv4() File "/usr/lib/sabnzbd/sabnzbd/getipaddress.py", line 114, in publicipv4 result = addresslookup4(sabnzbd.cfg.selftest_host()) File "/usr/lib/sabnzbd/sabnzbd/getipaddress.py", line 48, in func_wrapper return sabnzbd.THREAD_POOL.submit(item, *args, **kwargs).result(max_timeout) File "/usr/lib/python3.10/concurrent/futures/_base.py", line 448, in result raise TimeoutError() concurrent.futures._base.TimeoutError

What endpoint are you using? Does it continue to work if you restart your container?

I'm also experiencing this issue. I suspect it's related to PIA's WireGuard API, as my OpenVPN clients are working fine. Guess the only thing we can do is wait it out...?

Are there any plans for a new stable release for this container? The `2.0.3-2-01` version is pretty unreliable with PIA for me, but one of my trackers (MAM) doesn't allow any `-dev` tagged clients.