Page 1 of 1
Well, sorry I did the update to 1.0...
Posted: April 16th, 2016, 2:52 pm
by Warborg
Been working on various projects this morning and during a lull I figured I'd do the update to 1.0 as I figured it'd just be a quick one... Glad I did it on my workstation and not my server. Now it won't load at all no matter what... I did the update, and it came up asking for username/password (which I didn't set on initial install to the best of my recollection) so I hit cancel... Now I can't access it at all (yes, I did add /sabnzbd to the end of the URL, no joy). If I right click on the system tray icon to go to "show interface" I get the following (interesting as it used to be on 8080, and I am using Chrome but tried Edge and Firefox to similar results):
This site can’t be reached
The webpage at
http://192.168.0.111:119/sabnzbd/ might be temporarily down or it may have moved permanently to a new web address.
ERR_UNSAFE_PORT
So... so far (thumbsdown).
Re: Well, sorry I did the update to 1.0...
Posted: April 16th, 2016, 3:36 pm
by Warborg
Well, I decided to just start over... This think is just acting completely wacky. I got it running and configured again, and then after a restart it started asking for a username/password again that I did NOT set. I followed the FAQ and tried to edit them out but was still insisting on a u/p and wouldn't accept blanks. I put in what was in the .INI file and I got in. Checked the configuration and saw the u/p were populated still. So I cleared the fields and saved, and it rebooted and BAM can't load. Trying to show page comes back to the error I initially posted at port 119. I'm thinking this needs a little more QA time.
Re: Well, sorry I did the update to 1.0...
Posted: April 16th, 2016, 4:10 pm
by safihre
Your password manager or browser is filling the passwords of your Newsserver in the sabnzbd password field. Possibly even in the background, we've seen this before.
Even more, it is also filling the port number of your Newsserver. Port 119 is usenet default and sabnzbd would never use the port for its own service.
Try getting your browser or password manager (like Lastpass or Keypass) to stop filling it.
Re: Well, sorry I did the update to 1.0...
Posted: April 16th, 2016, 4:23 pm
by Warborg
I'll try that, thank you... I apologize for sounding harsh, I guess I shouldn't be tinkering after a bad night at work.
Re: Well, sorry I did the update to 1.0...
Posted: April 16th, 2016, 5:46 pm
by shypike
I see you are using port 119 for SABnzbd.
That will not work on OSX or Linux systems.
Which OS are you using?
Re: Well, sorry I did the update to 1.0...
Posted: April 16th, 2016, 5:54 pm
by Warborg
I think you were right, I think Lastpass might have been tripping it up. But I am seeing a different issue, when I am downloading the wastebin/delete button beside each item downloading does nothing. I can click on it all day long and it just keeps on downloading. Ideas?
Re: Well, sorry I did the update to 1.0...
Posted: April 16th, 2016, 5:56 pm
by Warborg
shypike wrote:I see you are using port 119 for SABnzbd.
That will not work on OSX or Linux systems.
Which OS are you using?
I wasn't using it, it was changing it to 119 on it's own... I believe the dev suggestion nailed it that lastpass kept populating that information when I was in the configuration and screwing it up... My intent was on using the default port... It's all working now. Except for the delete button thing I just posted.
Re: Well, sorry I did the update to 1.0...
Posted: April 17th, 2016, 1:37 am
by safihre
I think on one of the alerts you checked the box that's usually called something like 'Don't let this website show any more warnings' of your browser. So the confirmation if you want to delete for sure isn't shown anymore.
Usually this is reset after you restart the browser.
If not you can go click in sabnzbd on status and interface settings (you use the Glitter skin, right?) and go to Interface settings. If you uncheck there Confirm queue deletions, it should work without the confirmation box!