SABnzbd Forums

Suddenly SAB has stopped functioning in Firefox. Says it need a password and username but won't accept what I give it. I found the ini file so I know what it wants but it won't accept it. I did just upgrade to Docsis 3.0 today so perhaps it's a port issue? The port was set at 119. I'd certainly appreciate help with this.

Port 119 is the normal Usenet port, not SABnzbd's web port,
which usually is 8080.
Which operating system are you using?

I'm using port 119 and my OS is Win7 Ultimate. I did get the Firefox screen to open by clicking on the SAB icon and selecting troubleshoot/Restart without login so I guess it's something of a moot point but I still don't understand why it stopped accepting my username and password. SAB is currently downloading as long as I use the troubleshoot option to see what's happening.

On Window, SABnzbd's tray icon has the menu entry "Troubleshoot->Restart - no password".
Try that, and later set the username/password again.

The tray icon is what I used to select the "troubleshoot/Restart without login" but I don't see a "Troubleshoot->Restart - no password". Seems to be the same thing, though. I'll try resetting the unsername/password again. Thanks for your response.

That's what I meant

I just installed sabnzbd on the whatbox seedbox, went through the wizard, and now can't login. I enter the username and password I just used in the wizard and it just keeps saying authorization required. I even set the password to a simple word. I tried editing the .ini file too, but no luck. I'd appreciate any assistance.

Ah, a seedbox. I only hear about problems with that. Strange stuff as they seem to be not real VMs, but something like sharing systems ...

Anyway:

As you can edit sabnzbd.ini (like you say), you apparantly can login on the seedbox? If so, STOP sabnzbd. Make sure it is not running. Then access the SAB-URL again ... do you get a login? If so, that is NOT your SAB login screen ...

Thanks. Turns out it was the port number. Someone was using the port number from the directions. I picked a different port and it worked.

JED3141592 wrote:Thanks. Turns out it was the port number. Someone was using the port number from the directions. I picked a different port and it worked.

Exactly what I expected ... therefore the test with stopping SABnzbd ...

Good that it works now.