Google's chrom browser, after upgrading to version 63, if the domain name suffix accessed is .dev or .app, Google forces the use of https, and there is no way to skip it.
The reason is that Google took down the .dev top-level domain; in a September report , "Solutions for Chrome Upgrades," the impending problems with .dev were explained.
The solution is to modify: the sites section in Homestead.yaml, the file uses other suffix domain names to debug, such as modifying to .name .coop .localhost .test
but it must be an existing domain name address, if you randomly choose a domain name suffix or No domain suffix, such as .fuk, is not acceptable. Browsers will treat it as a keyword search:
Unable to access this site Could not find the server IP address for laravel.fuk. ● Do you want to visit http://laravel.com/? ● Please search Google for “laravel fuk” ERR_NAME_NOT_RESOLVED
After modifying Homestead.yaml, if the virtual machine is already running. Direct vagrant provision and then vagrant ssh, such as:
vagrant@homestead:~$ exit
E:\Homestead>vagrant provision
E:\Homestead>vagrant ssh
At the same time, don't forget, modify:
C:\WINDOWS\system32\drivers\etc\hosts file
192.168.10.10 laravel.test