127.0.0.1 refused to connect.
-
bluemax65 last edited by
Can anyone help me. I was on a site for a few days, everything was fine. However, suddenly, 2 days ago, I got the following error message when I tried to go back to the site.
This site can’t be reached
127.0.0.1 refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
Check your internet connection.
Check any cables and reboot any routers, modems, or other network devices you may be using.Allow Opera to access the network in your firewall or antivirus settings.
If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.If you use a proxy server…
Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server: Go to the Main menu > Settings > Change proxy settings… > LAN Settings and deselect "Use a proxy server for your LAN".I do not use a proxy server. My firewall is Zonealarm it was up and running the entire time I was on the site in the couple of weeks before I got the error message.
Every other site I was using at the time, and since is fine. It's just this one site.
Any suggestions as to what I can do?
Thanks.
-
blackbird71 last edited by
Some added thoughts: Did you or possibly some kind of software (including malware) alter your system's hosts file to place an entry in it that links the website's URL to the 127.0.0.1 'local hosts' computer internal IP? What antimalware programs do you use that may have blacklisted the site?
-
emniss last edited by
A few days ago, I had this problem too, when I was connected to one of the US American VPN servers. One URL (can't remember which one) was resolved to localhost. All other VPN locations were fine and connected to the site. So it might be a DNS problem (Opera VPN servers use their own DNS servers). If you are not using VPN, you should check your hosts file for unusual entries:
-
bluemax65 last edited by
I did at one point switch on the Opera VPN. What should I be looking for and change?
-
bluemax65 last edited by
I did. I then re-started Opera and the problem is still there, for that one website. I did try to access it using Firefox and Chrome, just now, and I can't do it. Same problem.
-
blackbird71 last edited by
If all your browsers are redirecting attempts to visit the site with similar error redirects to 127.0.0.1, it indicates something at your system level or your DNS look-up service is routing the connection attempts into your computer's 'local host' address rather than the IP address of the website.
The way it works is that when you attempt to visit an http or https website, that textual address must be converted into a numerical IP address (Internet Protocol) actually used to access sites on the Internet, a limited number of which IPs are dedicated by protocol purely to connect to local functions resident on the computer or its local network (such as 127.0.0.1). The look-up first occurs via your computer's own hosts file to see if there are any relevant URL conversions listed there, if not then your system/browser automatically consults the look-up listings in a specified DNS server out on the web. That DNS server will be either a default one from your provider or a user-defined one you've specified to the system. Once your system has retrieved the listed IP number for the URL you've entered, it attempts to make the actual connection to that IP.
If you are being directed to 127.0.0.1, it implies that either your browsers are being redirected by the computer's hosts file or a DNS server to an internal computer address instead of the desired IP, or your system is somehow misconfigured to access the internal address whenever you attempt to go out on the Internet. Since all the browsers show the problem for the site, and since other websites can be accessed OK, the implication is that something is redirecting that one unique website address back to the 127.0.0.1 local address. Depending on how the software operates, that means there either is a DNS/hosts incorrect address listing or that the DNS server cannot find an IP entry for the URL you're attempting to visit. In the latter case, one usually receives an error message indicating a non-existent URL, rather than the redirection to 127.0.0.1.