Page 1 of 1
10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 8th, 2014, 4:20 am
by mattyp73
I hope someone can help
- yes i have search the forum and read every post on this topic to no avail.
I have, as a test used another reader to test and I can connect and download from the same computer with the same server settings.
I can telnet to the news server I am using
sabdnzb just wont connect and i get a fail on the test
Any assistance would be appreciated
Thanks
Matt
Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 8th, 2014, 6:22 am
by shypike
Which timeout did you set in Config=>Servers?
Which provider is it?
Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 8th, 2014, 8:10 pm
by mattyp73
timeout set to 120
provider is tweaknews
Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 9th, 2014, 1:40 am
by shypike
Nothing wrong with either.
Do a test with another client to test your connectivity.
Try something basic like Grabit.
Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 12th, 2014, 8:50 am
by mattyp73
Thanks, i tried grabit and some other readers and they not working either.Looking at logs I noticed a typo in the port that I had not picked up, stupid error that cost me so much time.
Thanks for your help
Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 12th, 2014, 8:55 am
by mattyp73
okay, i take that back. It worked with the other software. I (for safety) reinstalled sabnzbd, out server details in, tested okay and software installed.
First attempt to download and nothing working.
If i go into setting and test the server I get the timeout.
So i close it all down and try again on SuperNZB and it works fine ?
Arrgh ?
Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 12th, 2014, 3:11 pm
by shypike
I have no idea.
I'm using tweaknews daily, albeit on a Mac.
Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 12th, 2014, 5:18 pm
by UNUser1981
I have the same exact problem, also with Tweaknews. I only noticed it about 3-4 days ago. The download seems completely dead except for a couple of minutes of activity at 1-2 kb/s download. I haven't changed anything in my configs and was using the provider for months without any problems. Not sure where to ask for the solution, since it seems to be the providers problem and not sabnzbd as there haven't been any changes there.
EDIT: Weirdly enough, it fixed itself, although I'm not sure what helped, because I did multiple things at once to try and fix it, stupidly. Deleted and readded SABNZBD in windows firewall, restartet SABNZBD (likely not it, because the problem persisted for days with several reboots of my PC) and restarted the router (most likely the root of the problem).
EDIT2: After the router reset the old speed was back for a couple of minutes, but it dropped quickly. So I changed the port to 443 SSL from 563 SSL as per this thread (
http://forums.sabnzbd.org/viewtopic.php?f=2&t=8866), since Tweaknews makes use of Astraweb, although I'm not with Virgin (I'm from Germany). My guess would be my provider is now blocking the 563 port?
Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 13th, 2014, 2:02 am
by mattyp73
boy, this is really frustrating, so i installed newsbin and set up server to tweaknews, astraweb and giganews. all work and files downloading.
same server settings in sabnzbd and i get this timeout message ... same message to all servers
this is really hurting my grey matter

Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 13th, 2014, 3:52 am
by sander
I would de-activate the Windows firewall, and try again.
EDIT: non-Microsoft firewalls and non-Microsoft virusscanners (!) on your Windows system can also be the cause of SABnzbd being blocked.
Re: 10061, "Failed to connect: (10060, 'timed out') -1@
Posted: April 14th, 2014, 5:41 pm
by hoswons
Had the same problem for the past week or so. Nothing changed on my side. Have been operating successfully for about 7-8 months. Switched from 563 to 443 and it worked right away. I have an email into Tweaknews for support and will call my ISP when I have a chance. 90% sure that it wasn't my ISP.