Comments on: Google Chrome 63: Goodbye .dev, Hello .test

By: Martin

Martin — Mon, 01 Oct 2018 14:24:12 +0000

Oh my word, this is a life saver. I have wasted soooo much time time trying to fix my installation!

Thanks so much!

By: Justin Foell

Justin Foell — Wed, 20 Dec 2017 16:22:44 +0000

In reply to mfs. Great suggestion. I added a little blurb right before the alternative TLDs section. Thanks!

By: mfs

mfs — Tue, 19 Dec 2017 20:36:38 +0000

In reply to Justin Foell. Probably makes sense to add these (temporary?) workarounds to the main article. A lot of people probably aren't going to scroll down and chip through the comments. Just a thought that could help.

By: Camilo Buitrago

Camilo Buitrago — Sat, 16 Dec 2017 01:14:44 +0000

Now I understand. I was finishing a site on my local machine and I usually use the .dev domain. It stopped working on Chrome so I have to finish it in Safari.

Now I understand why. Thanks for the tip, I will start using .test

By: Justin Foell

Justin Foell — Fri, 15 Dec 2017 21:26:41 +0000

In reply to Collins Agbonghama. Yep, Firefox, Opera, Safari and IE will be immune to this problem, at least for the time being. Google did purchase the .dev top level domain, so they eventually will start using it for public purposes.

By: Collins Agbonghama

Collins Agbonghama — Fri, 15 Dec 2017 20:59:58 +0000

I use Opera and apparently this doesn’t affect it. Perhaps at least not at the moment.

By: Justin Foell

Justin Foell — Fri, 15 Dec 2017 19:49:40 +0000

In reply to Tricia. I thought I was going mad when I first saw it as well. Then noticed I was running a newer version of chrome than a colleague who wasn't seeing the problem. Happy to help!

By: Tricia

Tricia — Fri, 15 Dec 2017 19:05:02 +0000

This explains a lot! All of the sudden I couldn’t access my local .dev sites. I lost the ability to hit the advanced button, set my site to ignore the warning, and get to work. It forced me to get serious about Local by Flywheel, which solved my problem. Thanks for putting this out there and giving me 3rd-party confirmation that I wasn’t just losing my mind!

By: Justin Foell

Justin Foell — Fri, 15 Dec 2017 16:36:50 +0000

In reply to Fabio Fava. Thanks for the tip Fabio!

By: Mic Sumner

Mic Sumner — Fri, 15 Dec 2017 16:04:10 +0000

In reply to Ben Attenborough.

Hi Ben,

By live staging site what did you mean? I’m guessing you’re referring to the subdomain? What’s happened refers to local development sites, because instead of using `localhost:81/about/`, you could change that to devsite.dev/about/. You aren’t allowed to use .com for local development sites, but now that Chrome treats .dev just like .com, then the browser will think hey this devsite.dev has got to mean something online! No, it wouldn’t check if you meant your local development site unfortunately.

If you would like HTTPS on your local development site, there are nice programs for this. If you’re already using a local development environment, check if your tool provides HTTPS support. I use Laragon to build my wordpress websites and it is great! Hey you know I could also recommend you try Flywheel Local as they can deal with the HTTPS for you local development environment. That tool is WordPress only but it does it magnificently and it’s pretty easy to use (and it’s free!).
Please let me know how it goes.

Kind regards,

Mic Sumner