Chrome 63 now forces .dev domains to HTTPS
-
Laragon uses .dev TLD as local virtual host tld by default, so I guess it's better to change the default to something.
https://laravel-news.com/chrome-63-now-forces-dev-domains-https
-
You can change the default in Hostname setting on the Preferences page.
And yes, the Laragon should change the default to something else like .test or .localhost or .devl etc.
I use .loc which is short for .localhost.
-
I switched to .loc but since I am using laravel I discovered that laravel still points to .dev, anyone has run into this problem?
-
We are free to overcome that mess. Many ways:
- Switch to Firefox.
- Change the hostname format
- Enable auto-generated SSL in Laragon
-
beautiful, laragon is awesome tool!
-
For that, you may have to change your hosts file entries which has .dev TLD to .loc TLD and also do change that in your {Laragon Root}\etc\apache2\sites-enabled or {Laragon Root}\etc\nginx\sites-enabled files.
-
@bantya Thanks for the tip, now working perfectly. Greetinfs from Chile.
-
@cristianmeza
š from India!
-
@leokhoa firefox nightly have it same as chrome, soon it will be in firefox:
-
@Samuell : Thanks for the heads-up. Laragon is now used
.oo
as default.
-
I changed from .oo to .dew
dewelopment
-
@nermamax
š
This seems like a nice workaround which is quite readable.
+1 for that š
-
@nermamax or can be changeto .test
-
+1
Laragon is just awesome! Thank you, Leo!