Chrome Localhost Connection Refused












7














This question is not a duplicate because the suggested duplicate does not solve this problem. There is no such flag on chrome://flags/.



I'm using the Google Chrome web browser and WampServer to locally host a website. When I try to see my website on the localhost address in Chrome I'm getting the error ERR_CONNECTION_REFUSED. When I type the IP address 127.0.0.1 instead, the result stays the same.





On the other hand, if I enter localhost into the address bar on Internet Explorer I'm getting the expected result: The webpage displayed.



How do I make Chrome's localhost work? It may be some sort of security measure but to me it's rather an annoyance than anything else.










share|improve this question




















  • 1




    What happens when you type http://127.0.0.1/ on both, and when you type http://[::1]/ on both?
    – grawity
    Aug 23 '15 at 13:54










  • @grawity Yes, both surprisingly work in Chrome and also on Internet Explorer. It seems like Chrome tries to do https://localhost/ but can't because a secure connection is not available.
    – BullyWiiPlaza
    Aug 23 '15 at 13:56








  • 3




    possible duplicate of Google Chrome can't access localhost domains
    – RiggsFolly
    Aug 24 '15 at 22:48






  • 2




    @RiggsFolly The given solution does not solve the problem though
    – BullyWiiPlaza
    Aug 25 '15 at 11:56












  • Google for Chrome and localhost Chrome has a few odd issues with localhost for some unknown reason. There are a few possible solutions, depending on your version and how many times the issue has been fixed and then re-occured.
    – RiggsFolly
    Aug 25 '15 at 12:05


















7














This question is not a duplicate because the suggested duplicate does not solve this problem. There is no such flag on chrome://flags/.



I'm using the Google Chrome web browser and WampServer to locally host a website. When I try to see my website on the localhost address in Chrome I'm getting the error ERR_CONNECTION_REFUSED. When I type the IP address 127.0.0.1 instead, the result stays the same.





On the other hand, if I enter localhost into the address bar on Internet Explorer I'm getting the expected result: The webpage displayed.



How do I make Chrome's localhost work? It may be some sort of security measure but to me it's rather an annoyance than anything else.










share|improve this question




















  • 1




    What happens when you type http://127.0.0.1/ on both, and when you type http://[::1]/ on both?
    – grawity
    Aug 23 '15 at 13:54










  • @grawity Yes, both surprisingly work in Chrome and also on Internet Explorer. It seems like Chrome tries to do https://localhost/ but can't because a secure connection is not available.
    – BullyWiiPlaza
    Aug 23 '15 at 13:56








  • 3




    possible duplicate of Google Chrome can't access localhost domains
    – RiggsFolly
    Aug 24 '15 at 22:48






  • 2




    @RiggsFolly The given solution does not solve the problem though
    – BullyWiiPlaza
    Aug 25 '15 at 11:56












  • Google for Chrome and localhost Chrome has a few odd issues with localhost for some unknown reason. There are a few possible solutions, depending on your version and how many times the issue has been fixed and then re-occured.
    – RiggsFolly
    Aug 25 '15 at 12:05
















7












7








7







This question is not a duplicate because the suggested duplicate does not solve this problem. There is no such flag on chrome://flags/.



I'm using the Google Chrome web browser and WampServer to locally host a website. When I try to see my website on the localhost address in Chrome I'm getting the error ERR_CONNECTION_REFUSED. When I type the IP address 127.0.0.1 instead, the result stays the same.





On the other hand, if I enter localhost into the address bar on Internet Explorer I'm getting the expected result: The webpage displayed.



How do I make Chrome's localhost work? It may be some sort of security measure but to me it's rather an annoyance than anything else.










share|improve this question















This question is not a duplicate because the suggested duplicate does not solve this problem. There is no such flag on chrome://flags/.



I'm using the Google Chrome web browser and WampServer to locally host a website. When I try to see my website on the localhost address in Chrome I'm getting the error ERR_CONNECTION_REFUSED. When I type the IP address 127.0.0.1 instead, the result stays the same.





On the other hand, if I enter localhost into the address bar on Internet Explorer I'm getting the expected result: The webpage displayed.



How do I make Chrome's localhost work? It may be some sort of security measure but to me it's rather an annoyance than anything else.







google-chrome internet-explorer localhost wamp






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 20 '17 at 10:16









Community

1




1










asked Aug 23 '15 at 13:51









BullyWiiPlaza

2781318




2781318








  • 1




    What happens when you type http://127.0.0.1/ on both, and when you type http://[::1]/ on both?
    – grawity
    Aug 23 '15 at 13:54










  • @grawity Yes, both surprisingly work in Chrome and also on Internet Explorer. It seems like Chrome tries to do https://localhost/ but can't because a secure connection is not available.
    – BullyWiiPlaza
    Aug 23 '15 at 13:56








  • 3




    possible duplicate of Google Chrome can't access localhost domains
    – RiggsFolly
    Aug 24 '15 at 22:48






  • 2




    @RiggsFolly The given solution does not solve the problem though
    – BullyWiiPlaza
    Aug 25 '15 at 11:56












  • Google for Chrome and localhost Chrome has a few odd issues with localhost for some unknown reason. There are a few possible solutions, depending on your version and how many times the issue has been fixed and then re-occured.
    – RiggsFolly
    Aug 25 '15 at 12:05
















  • 1




    What happens when you type http://127.0.0.1/ on both, and when you type http://[::1]/ on both?
    – grawity
    Aug 23 '15 at 13:54










  • @grawity Yes, both surprisingly work in Chrome and also on Internet Explorer. It seems like Chrome tries to do https://localhost/ but can't because a secure connection is not available.
    – BullyWiiPlaza
    Aug 23 '15 at 13:56








  • 3




    possible duplicate of Google Chrome can't access localhost domains
    – RiggsFolly
    Aug 24 '15 at 22:48






  • 2




    @RiggsFolly The given solution does not solve the problem though
    – BullyWiiPlaza
    Aug 25 '15 at 11:56












  • Google for Chrome and localhost Chrome has a few odd issues with localhost for some unknown reason. There are a few possible solutions, depending on your version and how many times the issue has been fixed and then re-occured.
    – RiggsFolly
    Aug 25 '15 at 12:05










1




1




What happens when you type http://127.0.0.1/ on both, and when you type http://[::1]/ on both?
– grawity
Aug 23 '15 at 13:54




What happens when you type http://127.0.0.1/ on both, and when you type http://[::1]/ on both?
– grawity
Aug 23 '15 at 13:54












@grawity Yes, both surprisingly work in Chrome and also on Internet Explorer. It seems like Chrome tries to do https://localhost/ but can't because a secure connection is not available.
– BullyWiiPlaza
Aug 23 '15 at 13:56






@grawity Yes, both surprisingly work in Chrome and also on Internet Explorer. It seems like Chrome tries to do https://localhost/ but can't because a secure connection is not available.
– BullyWiiPlaza
Aug 23 '15 at 13:56






3




3




possible duplicate of Google Chrome can't access localhost domains
– RiggsFolly
Aug 24 '15 at 22:48




possible duplicate of Google Chrome can't access localhost domains
– RiggsFolly
Aug 24 '15 at 22:48




2




2




@RiggsFolly The given solution does not solve the problem though
– BullyWiiPlaza
Aug 25 '15 at 11:56






@RiggsFolly The given solution does not solve the problem though
– BullyWiiPlaza
Aug 25 '15 at 11:56














Google for Chrome and localhost Chrome has a few odd issues with localhost for some unknown reason. There are a few possible solutions, depending on your version and how many times the issue has been fixed and then re-occured.
– RiggsFolly
Aug 25 '15 at 12:05






Google for Chrome and localhost Chrome has a few odd issues with localhost for some unknown reason. There are a few possible solutions, depending on your version and how many times the issue has been fixed and then re-occured.
– RiggsFolly
Aug 25 '15 at 12:05












2 Answers
2






active

oldest

votes


















0














Although I'm not using WampServer, I do get problems with Chrome refusing to access ports of localhost from time to time. I found clearing the cookies and files from the cache to resolve most of my issues.



This Quora article may also help.






share|improve this answer





























    0














    Open command prompt as Administrator and type these two commands one by one:



    netsh advfirewall firewall add rule name="TCP Port 80" dir=in action=allow protocol=TCP localport=80
    netsh advfirewall firewall add rule name="TCP Port 80" dir=out action=allow protocol=TCP localport=80


    After doing so, restart the Wamp server and try to access http://localhost.
    If that fails, try one of these links:
    http://127.0.0.1:80
    http://127.0.0.1:8080
    http://127.0.0.1:443
    http://127.0.0.1:4443

    Good luck!






    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f961532%2fchrome-localhost-connection-refused%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      Although I'm not using WampServer, I do get problems with Chrome refusing to access ports of localhost from time to time. I found clearing the cookies and files from the cache to resolve most of my issues.



      This Quora article may also help.






      share|improve this answer


























        0














        Although I'm not using WampServer, I do get problems with Chrome refusing to access ports of localhost from time to time. I found clearing the cookies and files from the cache to resolve most of my issues.



        This Quora article may also help.






        share|improve this answer
























          0












          0








          0






          Although I'm not using WampServer, I do get problems with Chrome refusing to access ports of localhost from time to time. I found clearing the cookies and files from the cache to resolve most of my issues.



          This Quora article may also help.






          share|improve this answer












          Although I'm not using WampServer, I do get problems with Chrome refusing to access ports of localhost from time to time. I found clearing the cookies and files from the cache to resolve most of my issues.



          This Quora article may also help.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 4 '16 at 1:19









          Zodman

          1032




          1032

























              0














              Open command prompt as Administrator and type these two commands one by one:



              netsh advfirewall firewall add rule name="TCP Port 80" dir=in action=allow protocol=TCP localport=80
              netsh advfirewall firewall add rule name="TCP Port 80" dir=out action=allow protocol=TCP localport=80


              After doing so, restart the Wamp server and try to access http://localhost.
              If that fails, try one of these links:
              http://127.0.0.1:80
              http://127.0.0.1:8080
              http://127.0.0.1:443
              http://127.0.0.1:4443

              Good luck!






              share|improve this answer


























                0














                Open command prompt as Administrator and type these two commands one by one:



                netsh advfirewall firewall add rule name="TCP Port 80" dir=in action=allow protocol=TCP localport=80
                netsh advfirewall firewall add rule name="TCP Port 80" dir=out action=allow protocol=TCP localport=80


                After doing so, restart the Wamp server and try to access http://localhost.
                If that fails, try one of these links:
                http://127.0.0.1:80
                http://127.0.0.1:8080
                http://127.0.0.1:443
                http://127.0.0.1:4443

                Good luck!






                share|improve this answer
























                  0












                  0








                  0






                  Open command prompt as Administrator and type these two commands one by one:



                  netsh advfirewall firewall add rule name="TCP Port 80" dir=in action=allow protocol=TCP localport=80
                  netsh advfirewall firewall add rule name="TCP Port 80" dir=out action=allow protocol=TCP localport=80


                  After doing so, restart the Wamp server and try to access http://localhost.
                  If that fails, try one of these links:
                  http://127.0.0.1:80
                  http://127.0.0.1:8080
                  http://127.0.0.1:443
                  http://127.0.0.1:4443

                  Good luck!






                  share|improve this answer












                  Open command prompt as Administrator and type these two commands one by one:



                  netsh advfirewall firewall add rule name="TCP Port 80" dir=in action=allow protocol=TCP localport=80
                  netsh advfirewall firewall add rule name="TCP Port 80" dir=out action=allow protocol=TCP localport=80


                  After doing so, restart the Wamp server and try to access http://localhost.
                  If that fails, try one of these links:
                  http://127.0.0.1:80
                  http://127.0.0.1:8080
                  http://127.0.0.1:443
                  http://127.0.0.1:4443

                  Good luck!







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Apr 21 at 15:34









                  Nurudin Imsirovic

                  27017




                  27017






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f961532%2fchrome-localhost-connection-refused%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Index of /

                      Tribalistas

                      Listed building