SABnzbd Forums

Hello all

I have recently began to use Usenet and Sab (official linuxserver docker) in my Unraid server. But ever since the update to version 3.0.2 [51cc765] i have been hit with these messages every time i start a download:

WARNING 2 hours ago Server XXX1 will be ignored for 10 minutes
WARNING 2 hours ago Cannot connect to server XXX1 [Server name does not resolve]
WARNING 2 hours ago Server XXX2 will be ignored for 10 minutes
WARNING 2 hours ago Cannot connect to server XXX2 [Server name does not resolve]
WARNING 2 hours ago Server XXX3 will be ignored for 10 minutes
WARNING 2 hours ago Cannot connect to server XXX3[Server name does not resolve]

Witch server is going to throw that warning message out is kind of random, and when i test the connection on the settings theres no error message. Also theres no error message in my DNS lookup. Anyone has some insight on what might be causing this problem? Thanks for your help.

PS: In Sab should i configure providers who have more than one server separately for higher success chances? for instance, should i enable both the american and European usenetprime servers separately or their content is identical and this is redundant?

Server name does not resolve

That is a DNS problem.

Also theres no error message in my DNS lookup.

How do you check that?

To circumvent DNS problems, you can fill out the IP adress of the newsserver. But SSL checking must then be turned off.

Best of course to solve DNS problems, but you say you don't have them ...

sander wrote: ↑August 31st, 2020, 3:47 pm

Server name does not resolve

That is a DNS problem.

Also theres no error message in my DNS lookup.

How do you check that?

To circumvent DNS problems, you can fill out the IP adress of the newsserver. But SSL checking must then be turned off.

Best of course to solve DNS problems, but you say you don't have them ...

On the status and interface options on sab itself i can see the DNS lookup is showing OK

Is there any privacy or security downside to changing to the IP address of the newsserver and turning off SSL checking?

Just to be clear only some servers have this error, the rest work perfectly.

Of course

Could also be a temporary glitch unrelated to the update, maybe your ISP's DNS's were just slow recentlty.