Changing folder permissions on a certain folder in vagrant synced folder path

[Ap Seh]

Hi,  

I have set the folder permissions of my synced folder in the vagrant file as 

config.vm.synced_folder ".", "/vagrant", 

owner: "vagrant",

group: "www-data",

mount_options: ["dmode=775,fmode=664"]

I want to selectively change the folder permissions of the folder restricted in this path /vagrant/www/myproject/restricted/. Say I wish to change that too 750, and the files inside it to 640, how can I accomplish this?

Thanks loads

[Alvaro Miranda Aguilera]

Hello

The easiest will be you leave ".", "/vagrant" as is

and you create more synced_folder for each requirement you have.

you can have 2 or 3, or as many as you need.

Alvaro.

--
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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/413b5878-b115-476a-9050-65d24e0bb20d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Ap Seh]

Hi Alvaro, 

Thanks loads for that tip. 

However I would like to point out that the folder "restricted" lies in the same path where I have previously set the "dmode=775,fmode=664".

hmmm so I want to set the permissions "dmode=775, fmode=664" down the folders  /vagrant/www/myproject/ and then set 

the permissions  "dmode=740,fmode=640" in the folder restricted  which lies here /vagrant/www/myproject/restricted/. 

So which vagrant commands would let me selectively target only the "restriced" folder in this path and not change the permissions for the entire path ? 

Sorry if I misunderstood something in your previous reply. I am very new to vagrant and I believe that changing permissions through vagrant changes them all down the path.

Any help appreciated, 

Thanks loads again for your time and help, 

Ajoo.

You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/R2gPXfXxnGQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exk6nz8m28H_BS5CgnQBD6Gp5iRwZKZoQYQ%3D13a5M%3DVRw%40mail.gmail.com.

[Alvaro Miranda Aguilera]

hello

vagrant is running commands so if nested folder permissions doesn't work is not a vagrant issue

if you were running vboxmanage share + mount on the guest wirthout vagrant you will probably hit the same issues.

nested mountpoint are usually troublesome, but this may work

config.vm.synced_folder ".", "/vagrant", 

  owner: "vagrant",

  group: "www-data",

  mount_options: ["dmode=775,fmode=664"]

config.vm.synced_folder "restricted", "/vagrant/restricted", 

  owner: "vagrant",

  group: "www-data",

  mount_options: ["dmode=750,fmode=640"]

[Ap Seh]

Hi Alvaro, 

Thanks loads for the reply. I'll check it out and revert in a while. 

I do have a hunch that this should work. 

Much obliged. 

Thanks loads !

Ajoo

--
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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/R2gPXfXxnGQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyFdoikWYGt93w1jgnjZaYrPvQ8GwBrc7jnNK2XuaTXvg%40mail.gmail.com.

[Ap Seh]

Hi Alvaro, 

Thanks for that great tip. It worked !!! I did have to modify it a bit though. Here's the exact code that I used 

config.vm.synced_folder "complete/path/to/folder/restricted", "/vagrant/path/upto/restricted", 

owner: "vagrant",

group: "www-data",

mount_options: ["dmode=750,fmode=640"]

That worked !!

Thanks loads once again !

Ajoo.

[Ap Seh]

Hi Alvaro, 

I would be grateful if you can confirm that the following commands in vagrantfile :

        config.vm.synced_folder "complete/path/to/folder/restricted", "/vagrant/path/upto/restricted", 

owner: "vagrant",

group: "www-data",

mount_options: ["dmode=750,fmode=640"]

actually replace the chown and chmod commands in linux. I mean that these commands in vagrant do what chown and chmod do in linux. 

Thanks loads and sorry if this is the most noob question. I would rather be sure. 

Thanks load.

Ajoo

[Alvaro Miranda Aguilera]

hello

almost

you could think have the same effect, but are not the same commands.

chown is to set the owner

chmod is to set the permissions

think on existing files and folder and you want to change them.

the ones you see in vagrant, are actually mount point and user owner of the mount point.

it doesn't run any chmod/chown command, but the result "looks the same"

by default will be vagrant user and some permissions, and you are overriding that.

but may or may not run chown/chmod.

hope this helps

Alvaro

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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CA%2BnFXPHtPXi9NgW8U2ogPy%2BXurNgLReNhtO%3DdkPx5uAOneP5%2Bg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Ap Seh]

Hi Alvaro, 

Yes that's what i meant I guess - an alternate to the linux commands in vagrant or what vagrant does to achieve the same effect as the chown and chmod commands. 

Sure it helps, 😃,

Thank you very much.

Ajoo

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eypekvJBmPf-OnS%2BYXk_U05fYWV4hkHgUAFubam8TLBiw%40mail.gmail.com.

[Ap Seh]

Hi, 

I had the misfortune of upgrading my VirtualBox version 5.1.14 to 5.1.16 and now my folders simply fail to mount. I ran the following command vagrant plugin install vagrant-vbguest & it did what it did. I checked my guest additions and they are the same version as my VirtualBox. There are no other errors that I get except towards the end i get the following message :

.

.

.

default] GuestAdditions 5.1.16 running --- OK.

==> default: Checking for guest additions in VM...

==> default: Configuring and enabling network interfaces...

==> default: Mounting shared folders...

    default: /vagrant => D:/test_p32

Vagrant was unable to mount VirtualBox shared folders. This is usually

because the filesystem "vboxsf" is not available. This filesystem is

made available via the VirtualBox Guest Additions and kernel module.

Please verify that these guest additions are properly installed in the

guest. This is not a bug in Vagrant and is usually caused by a faulty

Vagrant box. For context, the command attempted was:

mount -t vboxsf -o dmode=775,fmode=664,uid=1001,gid=33 vagrant /vagrant

The error output from the command was:

: No such file or directory

How can I get over this error and have my folders synced / shared !

Thanks loads.

   

[Alvaro Miranda Aguilera]

hello

try with a new VM.

mkdir precise64

cd precise64

vagrant init -m hashicorp/precise64

vagrant up

The error you are having, its common if you update everything on the guest, including kernel, if this happen a rebuild of virtualbox modules is required.

Does this happen even on a new box?

Alvaro.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CA%2BnFXPGKb-GqitT%2BzuVBQo1nPQEBW5punLZePtvec4DH6mb%3DTA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Ap Seh]

H Alvaro, 

Thanks for the response. 

I tried a number of VM's on my old version of the virtualbox but only precise32 worked. 

I have not tried any other VM on my new virtualbox which I upgraded only yesterday. I will try and revert my results. 

Thanks loads for the suggestioin. Have a great day !

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyj_0anGEsNx9Djy-TvurqXUh_FESJd%2B631gsRwZbTPUA%40mail.gmail.com.

[Alvaro Miranda Aguilera]

Hello

If only precise32 bit worked, check you can run 64 bits at all.

Since many of the VMs are 64 bits.

Try to start a VM 64 bits manually, and see if you get errors. Most of the time the VT extension required to run 64 bits are disabled, other times some CPUs like tablets can't enable this features.

Check the manual of your computer on how to enable this VT extensions on the Bios.

Thanks

Alvaro

[Ap Seh]

Hi Alvaro,  

Thanks again for your reply and interest in this issue. 

I would have tried the 64-bit versions but my Host is a Windows 32 bit machine and I was advised that it is not possible to run a 64-bit host on a 32 bit machine. So i never tried installing the 64-bit VM ever. If you think that this is incorrect and I can install a 64-bit VM on my windows 32bit machine, I'll try it out. 

Await your return,

Thanks loads, 

Ajoo. 

--

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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/R2gPXfXxnGQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ez7uZmgNpcqP%3DBbTspLSTtnzHxxhPZ9jbLSC-wY59AsYQ%40mail.gmail.com.

[Ap Seh]

Hi Alvaro, 

Hope you are doing good.

So I tried trusty32 and bento32 but they both either go into an invalid state after executing :-

    default: SSH username: vagrant

    default: SSH auth method: private key

goes into an invalid state 

OR 

I get the index.lock(Error::EACCES) like below :

    default: SSH username: vagrant

    default: SSH auth method: private key

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/machine_i ndex.rb:321:in `initialize': Permission denied @ rb_sysopen - C:/Users/Acer /.vagrant.d/data/machine-index/index.lock (Errno::EACCES)

        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagr ant/machine_index.rb:321:in `open'

        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagr ant/machine_index.rb:321:in `with_index_lock'

        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagr ant/machine_index.rb:192:in `block in set'

.

.

.

Totally stuck here !😨

[Alvaro Miranda Aguilera]

On Mon, Mar 13, 2017 at 12:24 PM, Ap Seh <apse...@gmail.com> wrote:

C:/Users/Acer

Hello

the best is open a cmd.exe window

and go to a directory insude your user.

see if you can create a directory

and do the vagrant init -m hashicorp/precise32

vagrant up

per your message, is seems there is no access to C:/Users/Acer home directory from the user you are using.

--

Alvaro

[Ap Seh]

Hi, 

Thanks for that direction. 

I am able to create a directory in C:/users/Acer. and then do the vagrant up from there.

The first time it downloaded the box and came to the command 

Booting VM.. and then went into an invalid state. 

After a vagrant halt and vagrant up again, it continues past that point and removed the in-secure and installed a new one, then updated the Guest versions that were not matching with the version of Virtual Box. 

Gave the following error :

Got different reports about installed GuestAdditions version:

Virtualbox on your host claims:   4.2.0

VBoxService inside the vm claims: 5.1.16

Going on, assuming VBoxService is correct...

Got different reports about installed GuestAdditions version:

Virtualbox on your host claims:   4.2.0

VBoxService inside the vm claims: 5.1.16

Going on, assuming VBoxService is correct...

Got different reports about installed GuestAdditions version:

Virtualbox on your host claims:   4.2.0

VBoxService inside the vm claims: 5.1.16

Going on, assuming VBoxService is correct...

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

    default: SSH username: vagrant

    default: SSH auth method: private key

==> 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

The guest machine entered an invalid state while waiting for it

to boot. Valid states are 'starting, running'. The machine is in the

'unknown' state. Please verify everything is configured

properly and try again.

By the way, I even tried the vagrant up with the GUI enabled and it gets stuck waiting for the network devices and waits for like 120 seconds and continues without the settings for that and it happens again down the line and finally it boots there. Meanwhile the bash window times out saying another process, (the GUI is accessing the processes)

Last evening I tried this for trusty32 and for bento32, but this is what happened each time OR it got stuck with no access at the index,lock files.

Should I revert back to the previous version of VB? Any other option ?

Thanks loads !

--
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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/R2gPXfXxnGQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyNh-ndL1ktdsQ-E0g-yfWEtPCdW0VjQ7vKfzV0H3JnsQ%40mail.gmail.com.

[Alvaro Miranda Aguilera]

On Tue, Mar 14, 2017 at 3:39 AM, Ap Seh <apse...@gmail.com> wrote:

Virtualbox on your host claims:   4.2.0

hello

seems you got a very old virtualbox version

Can you ensure you are on current vagrant and current virtualbox ?

vgarant by default won't do anything with the virtualbox so I will suggest remove vagrant-vbguest plugin if installed until you get some boxes up and running, so we can be sure core vagrant work

hashicorp/precise32 should work

--

Alvaro

[Ap Seh]

Hi, 

Here's the version information : 

      VirtualBox Graphical User Interface

      Version 5.1.16 r113841 (Qt5.6.2) 

and 

C:\Users\Acer\precise32>vagrant version

Installed Version: 1.9.1

Latest Version: 1.9.2

To upgrade to the latest version, visit the downloads...

I'll remove the vagrant vbguest plugin if it's installed. For this version (Hashicorp precise32) I did not install any plugins unless it's being picked up from the other previous installs of the different VMs. I hope I make sense there. 

Await your response, 

Thanks very much !

Ajoo.

--
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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/R2gPXfXxnGQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyJOJ%2BO08Ztz%3DpWAvX-QWL%3DHPQWXPDTW-gsLmLr9fqP7w%40mail.gmail.com.

[Ap Seh]

Hi, 

Here's the latest run of the vagrant up 

==> 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

==> default: Machine booted and ready!

[default] GuestAdditions 5.1.16 running --- OK.

==> default: Checking for guest additions in VM...

==> default: Mounting shared folders...

    default: /vagrant => C:/Users/Acer/precise32

Vagrant was unable to mount VirtualBox shared folders. This is usually

because the filesystem "vboxsf" is not available. This filesystem is

made available via the VirtualBox Guest Additions and kernel module.

Please verify that these guest additions are properly installed in the

guest. This is not a bug in Vagrant and is usually caused by a faulty

Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

: No such file or directory

C:\Users\Acer\precise32>vagrant vbguest --status

[default] GuestAdditions 5.1.16 running --- OK.

So yes, there is the guest additions running and Ok too. Yet the mount fails. The behavior of the boot through process is erratic. This is the first time it went through till here. 

Awaiting your advice, 

Thanks loads, 

Ajoo.

[Alvaro Miranda Aguilera]

On Tue, Mar 14, 2017 at 2:54 PM, Ap Seh <apse...@gmail.com> wrote:

    default: SSH auth method: private key

==> default: Machine booted and ready!

If this machine was created before, can you destroy it and do a new vagrant up?

vagrant destroy

vagrant up --no-provision

and please share all the output and the Vagrantfile.

Thanks!

--

Alvaro

[Alvaro Miranda Aguilera]

Hello

Checking other thread on this same mailing list, it seems there are some issues with 5.1.16 and Windows host 

can you try VirtualBox 5.1.14  ??

[Ap Seh]

Hi Alvaro, 

Thanks for the reply. Find below the output of the vagrant up you desired :

C:\Users\Acer\precise32>vagrant up --no-provision

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Importing base box 'hashicorp/precise32'...

==> default: Matching MAC address for NAT networking...

==> default: Checking if box 'hashicorp/precise32' is up to date...

==> default: Setting the name of the VM: precise32_default_1489652703479_30803

==> default: Clearing any previously set network interfaces...

==> default: Preparing network interfaces based on configuration...

    default: Adapter 1: nat

==> default: Forwarding ports...

    default: 22 (guest) => 2222 (host) (adapter 1)

==> 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

The guest machine entered an invalid state while waiting for it

to boot. Valid states are 'starting, running'. The machine is in the

'unknown' state. Please verify everything is configured

properly and try again.

If the provider you're using has a GUI that comes with it,

it is often helpful to open that and watch the machine, since the

GUI often has more helpful error messages than Vagrant can retrieve.

For example, if you're using VirtualBox, run `vagrant up` while the

VirtualBox GUI is open.

The primary issue for this error is that the provider you're using

is not properly configured. This is very rarely a Vagrant issue.

C:\Users\Acer\precise32>

I even tried after installing the vbguest plugin, but same result as above. 

My last version of VirtualBox was 5.1.14 and that, even though erratic, was working. Erratic that i had to do a few machine halts or reloads for the mount to go through. At times it would get stuck on 

    default: SSH auth method: private key . 

Again reloading, or destroying and vagrant up would get it working. 

So you suggest that I go back to the version 5.1.14 of the Virtual Box ?

Thank you very much, 

Ajoo.

[Ap Seh]

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)
• Shared Folders: fixed access to long pathes (5.1.16 regression; Windows guests only; bugs #14651, #16564)
• API: fixed snapshot handling of medium attachments and PCI device attachments (bug #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)
• Windows Additions: fixed automatic logins for Windows Vista and newer (5.1.4 regression; bug #15904)

Will upgrade and revert if the issue is resolved. It should be according to the above. 

Thanks very much.

[Ap Seh]

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

    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 !

[Ap Seh]

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.

  

[Alvaro Miranda Aguilera]

Hello.

As long all the devices trying to reach the forwarded port are on the same network, and the network allow guest to guest communication, should be fine.

if you could test on a separate network, will help you to confirm this.

There is nothing vagrant new version that should stop this from working.

alvaro

--
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 vagrant-up+unsubscribe@googlegroups.com.

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.

--

Alvaro

[Robert Lilly]

Since you can access the site on your mobile device by the IP address this is a DNS lookup issue. You'll need to edit the hosts file on your mobile device with 192.168.43.36  newproject.com just like you did on your Windows machine. How to do that will depend on what OS you're using and whether you can get either root or sudo access.

[Ap Seh]

Hi Alvaro and Robert, 

Thanks for the reply and suggestions.

I think I understand what is happening but why that I am not sure since I know only a wee bit about networking. I think that if I am using my mobile network, then I am able to get this connectivity on all devices that share this hot-spot wifi on my mobile. However if I am using my office wifi, then I am not able to connect my website from the other devices on this wifi network. I have no idea why? 

Maybe you guys can shed some light on this. 

Thanks loads, 

Ajoo.

--
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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/R2gPXfXxnGQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/012771a1-2f93-401d-9ed9-0c74708f573b%40googlegroups.com.

[Alvaro Miranda Aguilera]

check what IP you get on your wifi, and use the IP to test

first on the same computer then from other computer in the network

if IP fails, check if the Firewall on the computer is on, and try to disable it for a test

Alvaro

Virusvrij. www.avast.com

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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CA%2BnFXPE-bk%2BA9fYhp73nOpNRSm7uQRT0R0VnbUK_0VYTKvD16Q%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro