Page 1 of 1
Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: December 23rd, 2024, 3:27 pm
by kingpham
Hi,
Long time user, since update pre 4.4.0/4.4.1 im unable to download with errors 'Server news.usenet.farm will be ignored for 10 minutes' and 'Cannot connect to server news.usenet.farm [Server name does not resolve]'.
Ive checked Servers and all correct but when test server, comes with error ' Server address "news.usenet.farm:563" is not valid.'.
Any help much appreciated.
Ive uninstalled the app and rebooted several times.
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: December 23rd, 2024, 3:46 pm
by sander
Do you have other newsservers defined? If so: do they work.
Via SABnzbd's Wrench, what do you see at "Nameserver / DNS Lookup "?
Via SABnzbd's Wrench, set logging to +DEBUG, and try again (and/or click on Test Server).
Then in sabnzbd.log find the lines below. Post them on pastebin, and post the url here like pastebin . com / blablabla (so spaces in it)
Code: Select all
2024-12-23 21:43:11,618::DEBUG::[downloader:218] Retrieving server address information for <Server: id=-1, host=news.usenet.farm:563>
2024-12-23 21:43:12,452::DEBUG::[happyeyeballs:172] Available addresses for news.usenet.farm (port=563, IPv4 or IPv6): 2 IPv4 and 2 IPv6
2024-12-23 21:43:12,463::DEBUG::[happyeyeballs:102] Happy Eyeballs connected to 2a00:1d38:fa:1001:119::4 (news.usenet.farm, port=563) in 7ms
2024-12-23 21:43:12,463::INFO::[happyeyeballs:205] Quickest IP address for news.usenet.farm (port=563, IPv4 or IPv6): 2a00:1d38:fa:1001:119::4 (news.usenet.farm)
2024-12-23 21:43:12,518::INFO::[newswrapper:351] -1@news.usenet.farm: Connected using TLSv1.3 (TLS_AES_128_GCM_SHA256)
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: January 18th, 2025, 6:29 am
by callidus
I've been having the exact same problem with news.usenet.farm. My SSL connections to other servers have been working fine.
Here's the relevant lines from my debug info (as requested above):
Code: Select all
2025-01-18 06:14:50,842::DEBUG::[downloader:218] Retrieving server address information for <Server: id=-1, host=news.usenet.farm:563>
2025-01-18 06:14:50,946::DEBUG::[happyeyeballs:172] Available addresses for news.usenet.farm (port=563, IPv4 or IPv6): 2 IPv4 and 2 IPv6
2025-01-18 06:14:50,947::DEBUG::[happyeyeballs:110] Happy Eyeballs failed to connect to 2a00:1d38:fa:1001:119::1 (news.usenet.farm, port=563) in 0ms
2025-01-18 06:14:50,968::DEBUG::[happyeyeballs:110] Happy Eyeballs failed to connect to 2a00:1d38:fa:1001:119::4 (news.usenet.farm, port=563) in 0ms
I've tried both with and without SSL and neither one is working.
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: January 18th, 2025, 6:45 am
by sander
It says:
Happy Eyeballs failed to connect to 2a00:1d38:fa:1001:119::1 (news.usenet.farm, port=563) in 0ms
And lines after that?
Because if IPv6 fails, HappyEyeballs should then proceed to IPv4.
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: January 18th, 2025, 7:20 am
by callidus
No, I'm not seeing any news.usenet.farm lines after that. After that it proceeds to start doing Request GET lines from the various *aars.
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: January 18th, 2025, 7:35 am
by sander
callidus wrote: ↑January 18th, 2025, 7:20 am
No, I'm not seeing any news.usenet.farm lines after that. After that it proceeds to start doing Request GET lines from the various *aars.
That's weird, because:
Available addresses for news.usenet.farm (port=563, IPv4 or IPv6): 2 IPv4 and 2 IPv6
So the resolving found 2 IPv4 and 2 IPv6. After failing ipv6, it should try thee ipv4.
What kind of setup do you have: OS, docker, etc?
At: SABnzbd -> Wrench -> Status what do you see? Leave out the first part of public IP addresses, like this
Local IPv4 address 100.115.92.199
Public IPv4 address x.y.45.236
IPv6 address 2001:bla:blla4200:216
fedc:a59e
Nameserver / DNS Lookup OK
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: January 18th, 2025, 7:48 am
by callidus
I'm running a docker container.
Local IPv4 address 10.10.40.153
Public IPv4 address zzz.zzz.62.135
IPv6 address None
Nameserver / DNS Lookup OK
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: January 18th, 2025, 7:54 am
by sander
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: January 18th, 2025, 8:22 am
by callidus
Turned off ipv6_servers and restarted SAB and still getting the same error. After that I searched further in the logs and ended up finding the IPv4 HappyEyeballs entries. They weren't near the IPv6 ones, so I missed them before. Those were failing too with the same errors:
Code: Select all
2025-01-18 06:16:01,057::DEBUG::[happyeyeballs:215] Failed Happy Eyeballs lookup: No addresses could be resolved
2025-01-18 06:16:01,070::DEBUG::[happyeyeballs:110] Happy Eyeballs failed to connect to 178.20.174.249 (news.usenet.farm, port=119) in 5004ms
2025-01-18 06:16:01,092::DEBUG::[happyeyeballs:110] Happy Eyeballs failed to connect to 178.20.174.250 (news.usenet.farm, port=119) in 5005ms
I have two other news servers setup and those are both working without issue. So I decided to see if I could ping news.usenet.farm or its IP addresses from the docker container's CLI. Timed out there as well. So then I tested another container and got the same result.
After a few more tests, I've determined that PIA VPN appears to be blocking usenet.farm (or usenet.farm is blocking traffic from PIA).
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: January 18th, 2025, 8:29 am
by sander
callidus wrote: ↑January 18th, 2025, 8:22 am
After a few more tests, I've determined that PIA VPN appears to be blocking usenet.farm (or usenet.farm is blocking traffic from PIA).
Nice find!
"failed to connect to 178.20.174.250 (news.usenet.farm, port=119) in 5005ms" is indeed the time-out after 5 seconds.
Re: Cannot connect to server news.usenet.farm [Server name does not resolve]
Posted: January 18th, 2025, 8:37 am
by callidus
Thanks for the help @sander!
fedc:a59e