Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I have started on my third project on a Homestead setup for development. I recently updated Chrome Canary to the latest version (64) and now I can not access any of the projects, FireFox and IE still work. Chrome error is "ERR_SSL_SERVER_CERT_BAD_FORMAT". The security Tab in Developer tools adds that the "The connection to this site is using a valid, trusted server certificate issued by unknown name." So I assume it has something to do with the server certificate. Has anyone else encountered this with Chrome and Homestead combination?
Well Chrome is pushing to a more secure web. This means that they want all websites to run on HTTPS. Do you have anything setup for https for your homestead box?
If not you can follow this tutorial: https://laracasts.com/discuss/channels/tips/tip-how-to-enable-ssl-in-homestead-20?page=1
@bobbybouwmann Thanks, I've had quick look and most of it is way over my head. Servers are not my strong point which is why I went with Homestead in the first place, I thought this stuff was set up automatically for dopes like me. A lot of the posts in that article are quite old and I am reluctant to mess with stuff I do not understand.
I can access the project in Chrome using http://127.0.0.1:8000 however this only lets me access the most recent project. Is there a way to setup the hosts file to access all my projects via http://127.0.0.1:8000
It's not possible to link all your projects to the same http://127.0.0.1:8000 url. However you can get around this by using .localhost or .app domains in your homestead box.
For more information: https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/
@bobbybouwmann Big ups, changing the extension to *.test did the trick. Many Thanks.
Please or to participate in this conversation.