Laravel/Homestead vagrant machine issues when trying to access hosts
I have a very simple setup:
- Windows 10
- VirtualBox 6.0
- Vagrant 2.2.2
- Vagrant Host Updater plugin (to automatically set hosts from Vagrantfile)
- Laravel/Homestead 7 vagrant box
When I create this box (laravel/homestead-7), it has no errors. When I provision the box - no errors as well. I can even SSH into the box and access properly mapped folders between host/guest machines. But I have a problem with accessing the hosts: the hosts are automatically set with vagrant plugin upon running the machine, the problem is that those hosts are unreachable when trying to access it through browser or pinging from cmd (ex: ping homestead - returns General failure error. But I can ssh without no problem). The funny thing is - that sometimes it works properly without changing anything, but most of the time it is untrustworthy and when I need to do my work quickly - this becomes tedious. Also to note - I can share my environment from the inside the box with ngrok service which then allows me to use public URL to access my projects (which shows that the apache service inside the box is working properly or am I mistaken?).
I also have NordVPN, not sure if additional network drivers from this service might have caused this? Furthermore I have BitDefender as an antivirus/firewall, but I've made sure to add virtualbox headless, vagrant to the exception lists, also disabled hosts from being scanned/managed by the antivirus.
Could please someone help me with this? If anyone could give me atleast a tip where to start - I would be really thankful.
Pinging homestead
Hosts file entry from vagrant hosts plugin
Console output when starting the machine
virtualbox virtual-machine vagrant
asked Jan 15 at 12:25
Jonas PetrikJonas Petrik
12
add a comment |
I have a very simple setup:
- Windows 10
- VirtualBox 6.0
- Vagrant 2.2.2
- Vagrant Host Updater plugin (to automatically set hosts from Vagrantfile)
- Laravel/Homestead 7 vagrant box
When I create this box (laravel/homestead-7), it has no errors. When I provision the box - no errors as well. I can even SSH into the box and access properly mapped folders between host/guest machines. But I have a problem with accessing the hosts: the hosts are automatically set with vagrant plugin upon running the machine, the problem is that those hosts are unreachable when trying to access it through browser or pinging from cmd (ex: ping homestead - returns General failure error. But I can ssh without no problem). The funny thing is - that sometimes it works properly without changing anything, but most of the time it is untrustworthy and when I need to do my work quickly - this becomes tedious. Also to note - I can share my environment from the inside the box with ngrok service which then allows me to use public URL to access my projects (which shows that the apache service inside the box is working properly or am I mistaken?).
I also have NordVPN, not sure if additional network drivers from this service might have caused this? Furthermore I have BitDefender as an antivirus/firewall, but I've made sure to add virtualbox headless, vagrant to the exception lists, also disabled hosts from being scanned/managed by the antivirus.
Could please someone help me with this? If anyone could give me atleast a tip where to start - I would be really thankful.
Pinging homestead
Hosts file entry from vagrant hosts plugin
Console output when starting the machine
virtualbox virtual-machine vagrant
asked Jan 15 at 12:25
Jonas PetrikJonas Petrik
12
add a comment |
I have a very simple setup:
- Windows 10
- VirtualBox 6.0
- Vagrant 2.2.2
- Vagrant Host Updater plugin (to automatically set hosts from Vagrantfile)
- Laravel/Homestead 7 vagrant box
When I create this box (laravel/homestead-7), it has no errors. When I provision the box - no errors as well. I can even SSH into the box and access properly mapped folders between host/guest machines. But I have a problem with accessing the hosts: the hosts are automatically set with vagrant plugin upon running the machine, the problem is that those hosts are unreachable when trying to access it through browser or pinging from cmd (ex: ping homestead - returns General failure error. But I can ssh without no problem). The funny thing is - that sometimes it works properly without changing anything, but most of the time it is untrustworthy and when I need to do my work quickly - this becomes tedious. Also to note - I can share my environment from the inside the box with ngrok service which then allows me to use public URL to access my projects (which shows that the apache service inside the box is working properly or am I mistaken?).
I also have NordVPN, not sure if additional network drivers from this service might have caused this? Furthermore I have BitDefender as an antivirus/firewall, but I've made sure to add virtualbox headless, vagrant to the exception lists, also disabled hosts from being scanned/managed by the antivirus.
Could please someone help me with this? If anyone could give me atleast a tip where to start - I would be really thankful.
Pinging homestead
Hosts file entry from vagrant hosts plugin
Console output when starting the machine
virtualbox virtual-machine vagrant
asked Jan 15 at 12:25
Jonas PetrikJonas Petrik
12
I have a very simple setup:
- Windows 10
- VirtualBox 6.0
- Vagrant 2.2.2
- Vagrant Host Updater plugin (to automatically set hosts from Vagrantfile)
- Laravel/Homestead 7 vagrant box
When I create this box (laravel/homestead-7), it has no errors. When I provision the box - no errors as well. I can even SSH into the box and access properly mapped folders between host/guest machines. But I have a problem with accessing the hosts: the hosts are automatically set with vagrant plugin upon running the machine, the problem is that those hosts are unreachable when trying to access it through browser or pinging from cmd (ex: ping homestead - returns General failure error. But I can ssh without no problem). The funny thing is - that sometimes it works properly without changing anything, but most of the time it is untrustworthy and when I need to do my work quickly - this becomes tedious. Also to note - I can share my environment from the inside the box with ngrok service which then allows me to use public URL to access my projects (which shows that the apache service inside the box is working properly or am I mistaken?).
I also have NordVPN, not sure if additional network drivers from this service might have caused this? Furthermore I have BitDefender as an antivirus/firewall, but I've made sure to add virtualbox headless, vagrant to the exception lists, also disabled hosts from being scanned/managed by the antivirus.
Could please someone help me with this? If anyone could give me atleast a tip where to start - I would be really thankful.
Pinging homestead
Hosts file entry from vagrant hosts plugin
Console output when starting the machine
virtualbox virtual-machine vagrant
virtualbox virtual-machine vagrant
asked Jan 15 at 12:25
Jonas PetrikJonas Petrik
12
asked Jan 15 at 12:25
Jonas PetrikJonas Petrik
12
edited Jan 15 at 12:44
Jonas Petrik
asked Jan 15 at 12:25
Jonas PetrikJonas Petrik
12
asked Jan 15 at 12:25
Jonas PetrikJonas Petrik
12
asked Jan 15 at 12:25
Jonas PetrikJonas Petrik
12
12
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394498%2flaravel-homestead-vagrant-machine-issues-when-trying-to-access-hosts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394498%2flaravel-homestead-vagrant-machine-issues-when-trying-to-access-hosts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
