Error 111 when trying to connect to 127.0.0.1 (SOLVED: proxy problem)

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
richeb
Newbie
Newbie
Posts: 3
Joined: April 27th, 2018, 11:48 am

Error 111 when trying to connect to 127.0.0.1 (SOLVED: proxy problem)

Post by richeb »

Here's the message I'm getting this morning when trying to connect:

ERROR
The requested URL could not be retrieved
The following error was encountered while trying to retrieve the URL: http://127.0.0.1:8080/sabnzbd/

Connection to 127.0.0.1 failed.

The system returned: (111) Connection refused

The remote host or network may be down. Please try the request again.

Your cache administrator is webmaster.

I'm running the latest version of Win 10 and have version 2.3.3 of SABnzbd, installed this morning.
User avatar
safihre
Administrator
Administrator
Posts: 5366
Joined: April 30th, 2015, 7:35 am
Contact:

Re: Error 111 when trying to connect to 127.0.0.1

Post by safihre »

Do you maybe have some virusscanner or other security software active?
Are you sure sabnzbd is running (is it in Task manager or your icons in the bottom right?).
Where do you get this error? The browser?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
User avatar
OneCD
Hero Member
Hero Member
Posts: 557
Joined: March 4th, 2017, 3:47 pm

Re: Error 111 when trying to connect to 127.0.0.1

Post by OneCD »

Hopefully, OP is also using their browser on the same machine SABnzbd is installed on. ;)
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
richeb
Newbie
Newbie
Posts: 3
Joined: April 27th, 2018, 11:48 am

Re: Error 111 when trying to connect to 127.0.0.1

Post by richeb »

Well, this is interesting. The problem is only happening with the Chrome browser. And with Chrome, I get the same error
message when trying to open Plex.

BUT, I have no problem accessing both Plex and SABnzbd with Edge and Firefox. So, it definitely seems to be a Chrome thing. Chrome has been my default browser; perhaps I'll have to change that. Any Chrome experts out there?

I appreciate the two replies. And, yes SABnzbd is running on the same machine as the browsers and is not being stopped by virus software. :)
User avatar
sander
Release Testers
Release Testers
Posts: 8830
Joined: January 22nd, 2008, 2:22 pm

Re: Error 111 when trying to connect to 127.0.0.1

Post by sander »

If you Google that error message in combination with "Chrome", the first hits are about proxy settings in Chrome. So check that you have NOT set a proxy in Chrome for 127.0.0.1
richeb
Newbie
Newbie
Posts: 3
Joined: April 27th, 2018, 11:48 am

Re: Error 111 when trying to connect to 127.0.0.1

Post by richeb »

Many thanks, Sander. I didn't realize that there was a proxy setting in effect, but there was from when I was using PureVPN. After resetting that, no more problems!

Thanks again.

I guess we can mark this inquiry as solved. :)
User avatar
sander
Release Testers
Release Testers
Posts: 8830
Joined: January 22nd, 2008, 2:22 pm

Re: Error 111 when trying to connect to 127.0.0.1

Post by sander »

richeb wrote: May 1st, 2018, 6:43 pm Many thanks, Sander. I didn't realize that there was a proxy setting in effect, but there was from when I was using PureVPN. After resetting that, no more problems!

Thanks again.

I guess we can mark this inquiry as solved. :)
... I've put it in the title ... so that Google will find it quickly ...
Post Reply