NZB Completion Checker 0.9a update #1
Okay, the first update is up! Thanks to NewsGroupReviews for the bug report! This update will affect all current NZBcc 0.9a users, as it changes the location of the servers.lst file. The file will now be stored in your AppData folder. You can just move your current servers.lst file into the AppData folder, in a new folder called “NZBcc”.
If you don’t know where the AppData folder is located, go to your start menu, and select “Run” (or press Windows+R). Then type %AppData%, and Windows Explorer will open the correct folder for you. Then you just have to create a folder called “NZBcc”, and copy your servers.lst right in there – easy 
If you don’t have any problems with the current build of NZBcc, it most likely because you are logged into Windows as Administrator. However, you really should update to the latest version
The download link has been updated, but you can also just click here
January 14th, 2012 at 17:06
Great work! Just the enhancements I was looking for. QQ: do you have any special logic when an SSL enabled server is on port 80? For some reason I get an “Authentication Failed” error message when trying to connect to us-secure.theusenet.com on port 80 with SSL enabled. I know the user/pw is correct because I tested it with another application. Any ideas? Thanks for the hard work!
January 14th, 2012 at 20:04
Port 80 should work just fine! I just investigated the problem with us-secure.theusenet.com, and the full error message I got was: The remote certificate is invalid according to the validation procedure. One of the reasons why you could receive this message, is if the server certificate has errors in it – it has expired or the name does not match (eg. the hostname “us-secure.theusenet.com” must appear JUST like that in the cerfiticate) or it is not signed by an authority you trust. In short, there is probably not much you can do about it!!
If I can find the time, I might have a look at a workaround!
January 15th, 2012 at 19:02
Here’s an article on ignoring bunk certificates. Not sure if you want to add this logic in, but it seems pretty straight forward. Maybe add a check box in settings to ignore invalid ssl cert. Just an idea. Thanks for all the hard work! http://blog.jameshiggs.com/2008/05/01/c-how-to-accept-an-invalid-ssl-certificate-programmatically/
January 17th, 2012 at 20:04
Hi Dan!
Update #2 should have a fix for you! Go check it out and report back please
January 27th, 2012 at 05:12
Sorry for the delay… I’m now getting “Unable to connect. Please check your settings!” I checked my settings twice, and it’s the same I have set in SABnzbd. Not sure what’s wrong.
January 27th, 2012 at 06:44
@Dan
Make sure you got the latest version and try again 
The lastest update should fix that
January 28th, 2012 at 06:12
That’s the problem, I do have the latest version. The above error is what I’m still getting. Any ideas?
January 28th, 2012 at 08:18
Yup, think I found the problem! Redownload the file, and try again
January 29th, 2012 at 02:21
Sorry Zoon… still doesn’t work
Same error as above.
January 29th, 2012 at 07:35
Odd… anyways, I have made a special debug build for you. It will print out more information to the log about your error. Download the .exe file here, and replace the current NZBcc.exe file. Send the content of the log to me… or just post it here
January 29th, 2012 at 17:50
“Stream was not readable.” – No error code either. Just the text.
January 29th, 2012 at 19:00
Not much to go after! What server are you using, and what port number?
February 1st, 2012 at 01:54
us-secure.theusenet.com:80
February 1st, 2012 at 07:29
Hi Dan!
I just have to make sure… when you enter the hostname, do you enter it like this: “us-secure.theusenet.com:80″, or do you remember to split the hostname and port number in to the two separate fields?
February 2nd, 2012 at 03:17
Ha! Sorry, my developer mindset sometimes comes out when I type. Yes, I have it split into two different fields.
February 2nd, 2012 at 05:47
LOL
Well, I tried creating a trial account with theusenet.com, and I didn’t have any problems connecting on port 80 (setting the SSL flag) – strange! Do you have problems connecting to other usenet providers?
Btw, can I mail you a new version to test?
February 3rd, 2012 at 02:00
I have problems with reader.xsusenet.com but that’s cause it’s a bad service. Hit or miss. No probs with Astraweb. Sure, email the file. Please zip/rar with a password so it will come through.
February 3rd, 2012 at 09:41
Hi again!
I made a special build for you here!
When you test the server settings, a small messagebox will appear afterwards with some debug info.
FYI, I made a small change that might enable you to connect!
February 4th, 2012 at 17:14
I get a page not found when i click the link
February 4th, 2012 at 19:26
My bad… small error in the link
please try again!
February 5th, 2012 at 05:53
Connected to: us-secure.theusenet.com port: 80
Using SSL
SSL Authenticate As Client
SSL certificate trouble – continue
Creating streams
—————————————
That’s all I got for ya.
February 5th, 2012 at 12:22
Nailed it, thanks
Redownload the latest release for the fix! You have been a great help 
February 5th, 2012 at 19:29
After entering in the details, I keep getting:
“No connection could be made because the target machine actively refused it 192.168.x.x.:119.
what gives?
February 5th, 2012 at 19:31
Why are you trying to connect to your own machine? If you are running Giganews accelerator (or similar), try “localhost” instead! If that doesn’t solve it, please let me know
February 5th, 2012 at 19:42
Looks like I figured it out. I have to add the nzb file in again after corrections to the server settings are made.
February 5th, 2012 at 21:03
Let me get this straight! First you added a server, then an NZB file to the queue, then you changed the server settings. Then when checking the NZB file, it used the previous settings, correct?