Sabz on Synology Connection issues: Server name does not resolve

[chrys6571]

I have been running Sabz on Synology for at least 9yrs. Just Sabz installed no docker. Until very recently I have been getting random connection issues when trying to DL something doesnt matter what it is.


2024-07-20 21:49:24,508::INFO::[notifier:157] Sending notification: Warning - Cannot connect to server news-us.newshosting DOT com [Server name does not resolve] (type=warning, job_cat=None)
2024-07-20 21:49:24,507::WARNING::[downloader:476] Cannot connect to server news-us.newshosting DOT com [Server name does not resolve]
2024-07-20 21:49:24,509::INFO::[notifier:157] Sending notification: Warning - Server news-us.newshosting DOT com will be ignored for 10 minutes (type=warning, job_cat=None)
2024-07-20 21:49:24,509::WARNING::[downloader:478] Server news-us.newshosting DOT com will be ignored for 10 minutes
2024-07-20 21:49:24,510::DEBUG::[downloader:199] Resetting article queue for <Server: news-us.newshosting DOT com:563>
2024-07-20 21:49:24,511::DEBUG::[downloader:1007] Set planned server resume news-us.newshosting DOT comm in 10 mins
2024-07-20 21:49:24,512::DEBUG::[downloader:214] Retrieving server address information for news-us.newshosting DOT com


Newshost says its not them, IM using google DNS and I can ping the host with no issue. Anyone run into this or know what the heck is going on?

[sander]

What are the 20 lines before that?

You can also post on pastebin.com, and post the URL here with spaces in it

[chrys6571]

https://pastebin dot com/8zHsTvJ6

Here the 20lines

[sander]

https://pastebin.com/8zHsTvJ6

266 lines .... but no "server name does not resolve". Pity

Code: Select all

$ cat Sabz\ Log.txt  | grep -i -e newshosting -e happyeyeballs
2024-07-20 21:49:04,466::DEBUG::[downloader:214] Retrieving server address information for news-us.newshosting.com
2024-07-20 21:49:24,495::DEBUG::[happyeyeballs:206] Failed Happy Eyeballs lookup: [Errno -3] Temporary failure in name resolution

This is how it looks on my SABnzbd, which is succesful.

Code: Select all

2024-07-22 00:10:44,735::DEBUG::[downloader:214] Retrieving server address information for news-us.newshosting.com
2024-07-22 00:10:44,907::DEBUG::[happyeyeballs:163] Available addresses for news-us.newshosting.com (port=563, IPv4 or IPv6): 2 IPv4 and 0 IPv6
2024-07-22 00:10:45,093::DEBUG::[happyeyeballs:100] Happy Eyeballs connected to 85.12.62.225 (news.iad.newshosting.com) in 185ms
2024-07-22 00:10:45,094::INFO::[happyeyeballs:196] Quickest IP address for news-us.newshosting.com (port=563, IPv4 or IPv6): 85.12.62.225 (news.iad.newshosting.com)
2024-07-22 00:10:45,096::DEBUG::[happyeyeballs:100] Happy Eyeballs connected to 85.12.62.251 (news.iad.newshosting.com) in 177ms
2024-07-22 00:10:45,423::INFO::[newswrapper:332] -1@news-us.newshosting.com: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)

OK, back to basics:

In SABnzbd: Wrench symbol (upper right corner), what does it say at
Public IPv4 address x.y.65.33 (no need to post the all bytes)
and
Nameserver / DNS Lookup OK

Plus:

what happens when you fill out as servers and click on Test Server:
news.newshosting.com
news.eweka.nl

[chrys6571]

Local IPv4 address x.x.40.4
Public IPv4 address x.x.134.209
IPv6 address None
Nameserver / DNS Lookup OK

Server tests:

Server address

news-us....newshosting.....com:563" is not valid.

news......newshosting.......com - Connection succesful, however i had issues with this server which caused me to switch to the news-us server.

news.....eweka........nl - Authentication failed, check username/password.

[chrys6571]

Just tested news.newshosting.com again and now i get this: Could not connect to news.newshosting.com on port 563. It appears that news.newshosting.com operates as a web server (port 80), possibly an indexer, not a usenet server. You have to fill a usenet server.

[chrys6571]

And I just tried news-us.........newshosting...................com which failed before and now connection successful....sigh...........