docker-compose.yml - Unable to connect to app via browser












0














I am a beginner to the Docker world. I am currently using Docker Toolbox so please pardon me if I posted this question at the wrong section of the forum. Thanks



I was trying out all the steps in parts 1 and 2 of the tutorial without any major issues - I was able to deploy the friendlyhello app and access it by keying in on my browser. However, the problem comes when I was trying part 4. After creating the docker-compose.yml and following the rest of the instructions, I was not able to access the app via my browser anymore with or with the curl command. It says connection was refused. I have attached screenshot of all the commands as well as the error along with this post.



Any ideas where I have gone wrong? Thanks in advance!!



enter image description here










share|improve this question



























    0














    I am a beginner to the Docker world. I am currently using Docker Toolbox so please pardon me if I posted this question at the wrong section of the forum. Thanks



    I was trying out all the steps in parts 1 and 2 of the tutorial without any major issues - I was able to deploy the friendlyhello app and access it by keying in on my browser. However, the problem comes when I was trying part 4. After creating the docker-compose.yml and following the rest of the instructions, I was not able to access the app via my browser anymore with or with the curl command. It says connection was refused. I have attached screenshot of all the commands as well as the error along with this post.



    Any ideas where I have gone wrong? Thanks in advance!!



    enter image description here










    share|improve this question

























      0












      0








      0







      I am a beginner to the Docker world. I am currently using Docker Toolbox so please pardon me if I posted this question at the wrong section of the forum. Thanks



      I was trying out all the steps in parts 1 and 2 of the tutorial without any major issues - I was able to deploy the friendlyhello app and access it by keying in on my browser. However, the problem comes when I was trying part 4. After creating the docker-compose.yml and following the rest of the instructions, I was not able to access the app via my browser anymore with or with the curl command. It says connection was refused. I have attached screenshot of all the commands as well as the error along with this post.



      Any ideas where I have gone wrong? Thanks in advance!!



      enter image description here










      share|improve this question













      I am a beginner to the Docker world. I am currently using Docker Toolbox so please pardon me if I posted this question at the wrong section of the forum. Thanks



      I was trying out all the steps in parts 1 and 2 of the tutorial without any major issues - I was able to deploy the friendlyhello app and access it by keying in on my browser. However, the problem comes when I was trying part 4. After creating the docker-compose.yml and following the rest of the instructions, I was not able to access the app via my browser anymore with or with the curl command. It says connection was refused. I have attached screenshot of all the commands as well as the error along with this post.



      Any ideas where I have gone wrong? Thanks in advance!!



      enter image description here







      docker docker-compose






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 16 at 6:25









      griffinleow

      214




      214
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I think about that the ip in curl command is wrong.



          You can run in "cmd"



          netstat -n | findstr 4000



          It will show the IP address that is listening on 4000 port.



          consolresult



          If you see 0.0.0.0 it's listening on all ip address so that you can try on localhost or 127.0.0.1 else use the specific address from result command.



          Greetings.






          share|improve this answer





















          • Thanks for your input. I realized I had to stop and remove containers that were running on port 4000 before I could run a new container. Hence, I went ahead and removed all images and containers before repeating the tutorial steps. However, now I am receiving 'time out' error
            – griffinleow
            Nov 16 at 7:58













          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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%2fstackoverflow.com%2fquestions%2f53332536%2fdocker-compose-yml-unable-to-connect-to-app-via-browser%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          I think about that the ip in curl command is wrong.



          You can run in "cmd"



          netstat -n | findstr 4000



          It will show the IP address that is listening on 4000 port.



          consolresult



          If you see 0.0.0.0 it's listening on all ip address so that you can try on localhost or 127.0.0.1 else use the specific address from result command.



          Greetings.






          share|improve this answer





















          • Thanks for your input. I realized I had to stop and remove containers that were running on port 4000 before I could run a new container. Hence, I went ahead and removed all images and containers before repeating the tutorial steps. However, now I am receiving 'time out' error
            – griffinleow
            Nov 16 at 7:58


















          0














          I think about that the ip in curl command is wrong.



          You can run in "cmd"



          netstat -n | findstr 4000



          It will show the IP address that is listening on 4000 port.



          consolresult



          If you see 0.0.0.0 it's listening on all ip address so that you can try on localhost or 127.0.0.1 else use the specific address from result command.



          Greetings.






          share|improve this answer





















          • Thanks for your input. I realized I had to stop and remove containers that were running on port 4000 before I could run a new container. Hence, I went ahead and removed all images and containers before repeating the tutorial steps. However, now I am receiving 'time out' error
            – griffinleow
            Nov 16 at 7:58
















          0












          0








          0






          I think about that the ip in curl command is wrong.



          You can run in "cmd"



          netstat -n | findstr 4000



          It will show the IP address that is listening on 4000 port.



          consolresult



          If you see 0.0.0.0 it's listening on all ip address so that you can try on localhost or 127.0.0.1 else use the specific address from result command.



          Greetings.






          share|improve this answer












          I think about that the ip in curl command is wrong.



          You can run in "cmd"



          netstat -n | findstr 4000



          It will show the IP address that is listening on 4000 port.



          consolresult



          If you see 0.0.0.0 it's listening on all ip address so that you can try on localhost or 127.0.0.1 else use the specific address from result command.



          Greetings.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 16 at 6:59









          Arcmop

          11




          11












          • Thanks for your input. I realized I had to stop and remove containers that were running on port 4000 before I could run a new container. Hence, I went ahead and removed all images and containers before repeating the tutorial steps. However, now I am receiving 'time out' error
            – griffinleow
            Nov 16 at 7:58




















          • Thanks for your input. I realized I had to stop and remove containers that were running on port 4000 before I could run a new container. Hence, I went ahead and removed all images and containers before repeating the tutorial steps. However, now I am receiving 'time out' error
            – griffinleow
            Nov 16 at 7:58


















          Thanks for your input. I realized I had to stop and remove containers that were running on port 4000 before I could run a new container. Hence, I went ahead and removed all images and containers before repeating the tutorial steps. However, now I am receiving 'time out' error
          – griffinleow
          Nov 16 at 7:58






          Thanks for your input. I realized I had to stop and remove containers that were running on port 4000 before I could run a new container. Hence, I went ahead and removed all images and containers before repeating the tutorial steps. However, now I am receiving 'time out' error
          – griffinleow
          Nov 16 at 7:58




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • 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%2fstackoverflow.com%2fquestions%2f53332536%2fdocker-compose-yml-unable-to-connect-to-app-via-browser%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

          How to change which sound is reproduced for terminal bell?

          Can I use Tabulator js library in my java Spring + Thymeleaf project?

          Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents