hello If you disable the AV/Firewall it works?
If yes, then is matter of finding what exclusion works. you could exclude by network you use http:/localhost:<port> ? then try to exclude localhost and 127.0.0.1 for all ports On Sat, Dec 1, 2018 at 1:51 PM Jonas Petrikas <johny....@gmail.com> wrote: > Hello, > > I hope that someone might help me with this situation: > > I use vagrant box (laravel/homestead) for local development which maps > ports 80/443 for apache/nginx server from within the box. I have no issues > at starting this vagrant virtual machine. Some time passes - and it seems I > cannot access previously available websites from within the box. The only > thing that has changed recently - my antivirus software: I've started using > BitDefender Total Security. > > I bilieve that this is the cause for this issue. So I've tried a lot of > things: > - Added VirtualBox all .exe processes as "Trusted" and exceptions from > real time scanning > - Added all Vagrant .exe processes as exceptions (same as for VirtualBox) > - Reviewed firewall rules, that it should give both UDP/TCP access for > both VirtualBox/Vagrant > - Tried disabling AV/Firewall while working with VM > - Playing with different settings in BitDefender > - Googling for any similar situation > > This didn't help... > > Am I missing something? Is there any procedure/proper way in setting > vagrant with AV/Firewall? > > And the funny thing is - on another PC running ESET NOD32 I have the same > problem! The main difference is that I cannot access websites from the > vagrant box at all (the virtual machine starts without any errors, I can > ssh into it as well, but websites which should be available cannot be > accessed) > > In both cases I get the same message from web browser - access is blocked > due to firewall. > > *So my main question is really simple*: what would be a proper action in > my case? How should I setup my development environment with vagrant while > I'm still protected with AV/Firewall? Any advice help would be really > appreciated! > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/2a402674-6138-4e04-bf22-379dc63f0973%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/2a402674-6138-4e04-bf22-379dc63f0973%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyPfacrhWdWfv_eoDWaihjyZUVxomtz7nDnFsvv8ORCgQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
