Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Erik Gratz
19,266 PointsEditing Hosts file on Windows does nothing - URGENT, INTERVIEW UPCOMING
In this video, he very easily edits the hosts file to let laravel.dev point to 127.0.0.1. I did the same on my Windows 10 machine in Notepad, running as an administrator, saved changes and nothing. None of the guides I have looked up show anything different happening inside the file.
Upon loading laravel.dev:8000, I get "laravel.dev sent an invalid response ERR_SSL_PROTOCOL_ERROR". I have tried googling that error and found nothing.
I have an interview next week that covers this material, I really need to learn it. Help? Anyone?
1 Answer
Steven Parker
231,275 PointsI had better luck with Google, I found a page with 8 suggestions on dealing with it:
- Set correct system date, time & region
- Clear browser cache and cookies
- Disable QUIC Protocol
- Disable extensions
- Remove your system’s hosts file
- Clear SSL State
- Lower your internet security and privacy level
- Temporarily disable your firewall and/or antivirus tools for a moment
There were also several YouTube videos about it.
Erik Gratz
19,266 PointsErik Gratz
19,266 PointsI GOT IT!
So for anyone else having this issue, listen up! This issue was caused by newer browsers (I used Chrome 73.0.3683.86 64-bit) having a setting to inherently distrust the .dev web domain.
Its really that simple.
I changed the homestead.yaml and the hosts file to point to laravel.test instead of laravel.dev and it works like a charm now. You may have to reprovision the virtual machine by running 'vagrant provision' in the console in your homestead directory on the host machine, which will change all those references.