Connect vagrant machine to virtualBox












1















Hi i am trying to set up my git Bash enviroment with vagrant via virtualBox but i am unsuccessfull. I am trying to open localhost:8080/xxxx, but it just loads and I think this is because this



I have the latest versions of both vagrant and virtualBox.
My commands:
"cd fullstack/vagrant",
"vagrant up"



but then i get the following :




Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 8000 (guest) => 8000 (host) (adapter 1)
default: 8080 (guest) => 8080 (host) (adapter 1)
default: 5000 (guest) => 5000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key Timed out while waiting for the machine to boot. This means that Vagrant was unable to communicate
with the guest machine within the configured ("config.vm.boot_timeout"
value) time period.



If you look above, you should be able to see the error(s) that Vagrant
had when attempting to connect to the machine. These errors are
usually good hints as to what may be wrong.



If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes. Verify
that authentication configurations are also setup properly, as well.



If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.











share|improve this question



























    1















    Hi i am trying to set up my git Bash enviroment with vagrant via virtualBox but i am unsuccessfull. I am trying to open localhost:8080/xxxx, but it just loads and I think this is because this



    I have the latest versions of both vagrant and virtualBox.
    My commands:
    "cd fullstack/vagrant",
    "vagrant up"



    but then i get the following :




    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
    ==> default: Clearing any previously set forwarded ports...
    ==> default: Clearing any previously set network interfaces...
    ==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    ==> default: Forwarding ports...
    default: 8000 (guest) => 8000 (host) (adapter 1)
    default: 8080 (guest) => 8080 (host) (adapter 1)
    default: 5000 (guest) => 5000 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
    ==> default: Running 'pre-boot' VM customizations...
    ==> default: Booting VM...
    ==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key Timed out while waiting for the machine to boot. This means that Vagrant was unable to communicate
    with the guest machine within the configured ("config.vm.boot_timeout"
    value) time period.



    If you look above, you should be able to see the error(s) that Vagrant
    had when attempting to connect to the machine. These errors are
    usually good hints as to what may be wrong.



    If you're using a custom box, make sure that networking is properly
    working and you're able to connect to the machine. It is a common
    problem that networking isn't setup properly in these boxes. Verify
    that authentication configurations are also setup properly, as well.



    If the box appears to be booting properly, you may want to increase
    the timeout ("config.vm.boot_timeout") value.











    share|improve this question

























      1












      1








      1


      1






      Hi i am trying to set up my git Bash enviroment with vagrant via virtualBox but i am unsuccessfull. I am trying to open localhost:8080/xxxx, but it just loads and I think this is because this



      I have the latest versions of both vagrant and virtualBox.
      My commands:
      "cd fullstack/vagrant",
      "vagrant up"



      but then i get the following :




      Bringing machine 'default' up with 'virtualbox' provider...
      ==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
      ==> default: Clearing any previously set forwarded ports...
      ==> default: Clearing any previously set network interfaces...
      ==> default: Preparing network interfaces based on configuration...
      default: Adapter 1: nat
      ==> default: Forwarding ports...
      default: 8000 (guest) => 8000 (host) (adapter 1)
      default: 8080 (guest) => 8080 (host) (adapter 1)
      default: 5000 (guest) => 5000 (host) (adapter 1)
      default: 22 (guest) => 2222 (host) (adapter 1)
      ==> default: Running 'pre-boot' VM customizations...
      ==> default: Booting VM...
      ==> default: Waiting for machine to boot. This may take a few minutes...
      default: SSH address: 127.0.0.1:2222
      default: SSH username: vagrant
      default: SSH auth method: private key Timed out while waiting for the machine to boot. This means that Vagrant was unable to communicate
      with the guest machine within the configured ("config.vm.boot_timeout"
      value) time period.



      If you look above, you should be able to see the error(s) that Vagrant
      had when attempting to connect to the machine. These errors are
      usually good hints as to what may be wrong.



      If you're using a custom box, make sure that networking is properly
      working and you're able to connect to the machine. It is a common
      problem that networking isn't setup properly in these boxes. Verify
      that authentication configurations are also setup properly, as well.



      If the box appears to be booting properly, you may want to increase
      the timeout ("config.vm.boot_timeout") value.











      share|improve this question














      Hi i am trying to set up my git Bash enviroment with vagrant via virtualBox but i am unsuccessfull. I am trying to open localhost:8080/xxxx, but it just loads and I think this is because this



      I have the latest versions of both vagrant and virtualBox.
      My commands:
      "cd fullstack/vagrant",
      "vagrant up"



      but then i get the following :




      Bringing machine 'default' up with 'virtualbox' provider...
      ==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
      ==> default: Clearing any previously set forwarded ports...
      ==> default: Clearing any previously set network interfaces...
      ==> default: Preparing network interfaces based on configuration...
      default: Adapter 1: nat
      ==> default: Forwarding ports...
      default: 8000 (guest) => 8000 (host) (adapter 1)
      default: 8080 (guest) => 8080 (host) (adapter 1)
      default: 5000 (guest) => 5000 (host) (adapter 1)
      default: 22 (guest) => 2222 (host) (adapter 1)
      ==> default: Running 'pre-boot' VM customizations...
      ==> default: Booting VM...
      ==> default: Waiting for machine to boot. This may take a few minutes...
      default: SSH address: 127.0.0.1:2222
      default: SSH username: vagrant
      default: SSH auth method: private key Timed out while waiting for the machine to boot. This means that Vagrant was unable to communicate
      with the guest machine within the configured ("config.vm.boot_timeout"
      value) time period.



      If you look above, you should be able to see the error(s) that Vagrant
      had when attempting to connect to the machine. These errors are
      usually good hints as to what may be wrong.



      If you're using a custom box, make sure that networking is properly
      working and you're able to connect to the machine. It is a common
      problem that networking isn't setup properly in these boxes. Verify
      that authentication configurations are also setup properly, as well.



      If the box appears to be booting properly, you may want to increase
      the timeout ("config.vm.boot_timeout") value.








      windows vagrant virtualbox git-bash






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 24 '18 at 12:44









      Lukas PeterssonLukas Petersson

      225




      225
























          1 Answer
          1






          active

          oldest

          votes


















          1














          solved. For anyone with a similar problem:



          I reinstalled both programs but this time I initialized a box within vagrant. I just picked the most popular from here: https://app.vagrantup.com/boxes/search






          share|improve this answer























            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%2f53458283%2fconnect-vagrant-machine-to-virtualbox%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









            1














            solved. For anyone with a similar problem:



            I reinstalled both programs but this time I initialized a box within vagrant. I just picked the most popular from here: https://app.vagrantup.com/boxes/search






            share|improve this answer




























              1














              solved. For anyone with a similar problem:



              I reinstalled both programs but this time I initialized a box within vagrant. I just picked the most popular from here: https://app.vagrantup.com/boxes/search






              share|improve this answer


























                1












                1








                1







                solved. For anyone with a similar problem:



                I reinstalled both programs but this time I initialized a box within vagrant. I just picked the most popular from here: https://app.vagrantup.com/boxes/search






                share|improve this answer













                solved. For anyone with a similar problem:



                I reinstalled both programs but this time I initialized a box within vagrant. I just picked the most popular from here: https://app.vagrantup.com/boxes/search







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 24 '18 at 21:59









                Lukas PeterssonLukas Petersson

                225




                225






























                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53458283%2fconnect-vagrant-machine-to-virtualbox%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

                    Contact image not getting when fetch all contact list from iPhone by CNContact

                    count number of partitions of a set with n elements into k subsets

                    A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks