Homestead / Vagrant – ‘This site can’t be reached’

Issue Description

When setting up a local dev site, the new URL returns ‘This site can’t be reached’. Other local URLs still work, however.

Provisioning, removing and re-adding the project doesn’t fix it.

Affected Browsers

Issue Type

Server / Hosting

How to Fix the Issue

To fix the issue, it’s worth trying to create a blank project at the end of the Homestead file to a static index file. Once re-provisioned, Homestead seems to kick back into picking up the dev URLs which fixes the problematic URL previously created.

What can also work (as of 29/07/2019) is to change the URL in gasmask and homestead.yaml. For example, change:

example.cargo

to:

example2.cargo

Once vagrant provisioned, change the domain name BACK to the original and then provision again.