newsbin.com

Search is down for me, but was working last night. Anyone else have the same problem?

EDIT: Log says "connection failed to: is.newsbin.com"

Working here right now. Wonder if your firewall is blocking it?

It's working again. I think it might have been the VPN. It was in some kind of catch-22 state, where it wouldn't connect because it said it was connected, but also wouldn't let me disconnect. Something to do with TAP, I think. Sorry for the bother.

Okay, so I'm still having the issue with not connecting to search. It seems like it's been getting progressively worse over the last couple of weeks. It's not the VPN, as I thought it was, because it happens when the VPN is not running. It's not the firewall, as it works about 50-60% of the time (until today, when it's been about every third search or so), and I would think the firewall would be blocking all, not just some searches. I thought it might have been my router, but new router, same old issue. It happens when I'm d/l ing other things, but also happens when I'm not. There doesn't seem to be any consistency to when it happens. Has anybody else seen this? Or is it just me?

How many download connections are you using? If you use an excessive number of connections, it doesn't leave much space for Newsbin to connect to the search server. As an experiment, you could pause all downloads and try searches without downloading and see if they're reliable.

I'm connected to Newsdemon, ND EU, and ND Dutch, with 20, 10, and 10 connections respectively. I dropped the ND one from 20 to 10, to see if that makes a difference. Should I drop them even more? I'm experiencing it a lot, even when I'm not downloading at all. I came back to the computer after a while to find a bunch of the errors (15 maybe?), and I wasn't downloading anything else at the time. I think those ones were cases of Newsbin going through my watchlists, and not being able to connect.

40 connections is a bunch. Is there any benefit to running that many? I get full speed with 10 connections.

The question I'm trying to answer is whether the number of connections is the cause of your problem. If it is, then maybe I can play with the connection timeouts so, the search connection is less likely to fail. If it's not then I need to look at other possibilities.

I think it was my internet provider. I just switched services yesterday, and haven't had it happen again. Don't know what was causing it, exactly, but it seems to have been rectified by the provider switch. I'll keep an eye on it and let you know if it happens again.

That's good to hear.