HI alvaro, Hope you are good. Been struggling with vagrant to get it to be accessed by other machines in the local network and this is something I had achieved with the previous version of vagrant before I upgraded to 5.1.16.
Now I am using the hotspot of my mobile. I have the server up and running and I have defined a virtualhost there in. I am able to access this virtual host from the Host machine by using the its name newproject.com. But if i try and access it on my mobile It says newproject.com's server DNS address could not be found. I am, however, able to reach, the index.html (default server page) from both my Host machine as well as the mobile using the ip address 192.168.43.36. I have defined : 192.168.43.36 newproject.com in the host file in both the Host Machine (Windows 7) as well as in the guest server ( precise32 ) though the definition in the guest server seems to make no difference. My network setting in the vagrantfile : *config.vm.network "public_network", ip: "192.168.43.36"* I am using the ondrej library for apache 2.4.25 version. Not getting this going is driving me nuts. I wonder how hard it would be to give internet access to this machine then. *😨🤔* Please help. 🙏 Thanks loads, Ajoo. On Thu, Mar 16, 2017 at 5:48 PM, Ap Seh <[email protected]> wrote: > Hi, > > With the new version, the folders mounted. It however kept the guest > additions of a previous version 4.30 or something. Here is the last bit of > the output. ( The entire was too long due to the guest additions which it > detected and tried to install ) > > *Restarting VM to apply changes...* > *==> default: Attempting graceful shutdown of VM...* > *==> default: Booting VM...* > *==> default: Waiting for machine to boot. This may take a few minutes...* > * default: SSH address: 127.0.0.1:2222 <http://127.0.0.1:2222>* > * default: SSH username: vagrant* > * default: SSH auth method: private key* > *==> default: Machine booted and ready!* > *==> default: Checking for guest additions in VM...* > * default: The guest additions on this VM do not match the installed > version o* > *f* > * default: VirtualBox! In most cases this is fine, but in rare cases it > can* > * default: prevent things such as shared folders from working properly. > If you* > * see* > * default: shared folder errors, please make sure the guest additions > within t* > *he* > * default: virtual machine match the version of VirtualBox you have > installed* > *on* > * default: your host and reload your VM.* > * default:* > * default: Guest Additions Version: 4.2.0* > * default: VirtualBox Version: 5.1* > *==> default: Mounting shared folders...* > * default: /vagrant => C:/Users/Acer/precise32* > > *C:\Users\Acer\precise32>vagrant up* > > > Thanks loads Alvaro ! > > > On Thu, Mar 16, 2017 at 4:43 PM, Ap Seh <[email protected]> wrote: > >> Hi, >> >> Was going to go back to 5.1.14 when I came across this. >> >> *VirtualBox 5.1.18* (released 2017-03-15) >> >> This is a maintenance release. The following items were fixed and/or >> added: >> >> - Shared Folders: fixed case insensitive filename access (5.1.16 >> regression; Windows guests only; bug #16549 >> <https://www.virtualbox.org/ticket/16549>) >> - Shared Folders: fixed access to long pathes (5.1.16 regression; >> Windows guests only; bugs #14651 >> <https://www.virtualbox.org/ticket/14651>, #16564 >> <https://www.virtualbox.org/ticket/16564>) >> - API: fixed snapshot handling of medium attachments and PCI device >> attachments (bug #16545 <https://www.virtualbox.org/ticket/16545>) >> - API: make 32-bit Windows guests in raw mode boot again if the ICH9 >> chipset is used (5.1.16 regression) >> - VBoxBugReport: fixed VM log collection issue >> - Linux hosts: fixed autostart service script (bug #14955 >> <https://www.virtualbox.org/ticket/14955>) >> - Windows Additions: fixed automatic logins for Windows Vista and >> newer (5.1.4 regression; bug #15904 >> <https://www.virtualbox.org/ticket/15904>) >> >> Will upgrade and revert if the issue is resolved. It should be according >> to the above. >> >> Thanks very much. >> >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CA%2BnFXPG%2BYA8R79NTtmy_mspf%2B8nnieb%3D9yWNGV_9BV-aaY-ahg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
