<p>Context: <a href="https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/" rel="nofollow noreferrer">https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/</a></p>

<p>The gist is that Chrome is forcing all .dev domains to use https (SSL) via HSTS.</p>

<p>If you want to continue to use a .dev domain, then you'll need to create a valid self-signed SSL cert and make sure OpenSSL is configured properly on your box.</p>

<p>Alternatively, you can swap to using something like craft.test because .test is reserved to never be used as an official top level domain. <a href="https://en.wikipedia.org/wiki/.test" rel="nofollow noreferrer">https://en.wikipedia.org/wiki/.test</a></p>

CC BY-SA 3.0
2017-10-06T08:43:32.680Z
Very interesting indeed. Thanks for your reply Brad. I'll confirm this as answered.
Daniel Van Cuylenburg
CC BY-SA 3.0
2017-10-05T13:59:38.760Z
2017-10-05T13:59:38.760Z
Brad Bell
<p>I'm not able to login to my local craft cms in google chrome canary, version 63.0.3233.0. I've attached a screenshot of the error message I've received when trying to go to the standard login page. I can log in fine on normal Chrome.</p>

<p>I know Canary is beta software of newer version of chrome, however, if they release this into the wild later on, is it something to worry about? I'm running MAMP free. Is it something that can be fixed with MAMP pro or? Any suggestions most welcome. Thanks :)</p>

<p><a href="https://i.sstatic.net/Id48u.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Id48u.png" alt="enter image description here"></a></p>

<craft-pro>
Can't access Craft CMS admin in Chrome Canary 63.0.3233.0
# Can't access Craft CMS admin in Chrome Canary 63.0.3233.0

(Asked by: username_0 on 2017-10-05)

I'm not able to login to my local craft cms in google chrome canary, version 63.0.3233.0. I've attached a screenshot of the error message I've received when trying to go to the standard login page. I can log in fine on normal Chrome.

I know Canary is beta software of newer version of chrome, however, if they release this into the wild later on, is it something to worry about? I'm running MAMP free. Is it something that can be fixed with MAMP pro or? Any suggestions most welcome. Thanks :)

[![enter image description here](https://i.sstatic.net/Id48u.png)](https://i.sstatic.net/Id48u.png)

**Tags:** craft-pro


---

## 1 answers

### Answer by username_1 on 2017-10-05. Score: 1

Context: <https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/>

The gist is that Chrome is forcing all .dev domains to use https (SSL) via HSTS.

If you want to continue to use a .dev domain, then you'll need to create a valid self-signed SSL cert and make sure OpenSSL is configured properly on your box.

Alternatively, you can swap to using something like craft.test because .test is reserved to never be used as an official top level domain. <https://en.wikipedia.org/wiki/.test>

> **Comments:**
> **username_0**: Very interesting indeed. Thanks for your reply Brad. I'll confirm this as answered.  

---

