# Updating domain name to .local SSL not verifying now **URL:** \ **Category:** Support\ **Created:** [December 13, 2017, 8:21pm UTC](https://community.localwp.com/t/updating-domain-name-to-local-ssl-not-verifying-now/4316 "2017-12-13T20:21:10Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![colegeissinger](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/colegeissinger/32/5318_2.png) [@colegeissinger](https://community.localwp.com/u/colegeissinger)\ **Post date:** [December 13, 2017, 8:21pm UTC](https://community.localwp.com/t/updating-domain-name-to-local-ssl-not-verifying-now/4316/1 "2017-12-13T20:21:10Z")
Due to Chrome 63 forcing HTTPS on .dev - [https://laravel-news.com/chrome-63-now-forces-dev-domains-https](https://laravel-news.com/chrome-63-now-forces-dev-domains-https) - I needed to update my domain name to a .local domain. Site is a WooCommerce site and is forcing HTTPS so I need SSL verification. Getting invalid certificate errors - # SEC\_ERROR\_UNKNOWN\_ISSUER Any clue on how I can fix this? I tried removing the certs in ~/Library/Application Support/Local by Flywheel/routes but no dice. ---
**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\ **Post date:** [December 13, 2017, 10:08pm UTC](https://community.localwp.com/t/updating-domain-name-to-local-ssl-not-verifying-now/4316/2 "2017-12-13T22:08:58Z")
Hi Cole, Since you’ve already changed the site domain, I’d try this: 1. Restart the site that you’re having this issue on 2. If the site is already selected in Local, click off of it onto another site and then back onto it. This will force some of the information on the site panel to refresh including the site’s certificate fingerprint that Local looks for in the system keychain. 3. Go to “SSL” tab and click “Trust” 4. Press Cmd + Shift + R in Chrome to do a hard refresh. This should force Chrome to look up the certificate in the keychain to see if it’s trusted. ---
**Author:** ![colegeissinger](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/colegeissinger/32/5318_2.png) [@colegeissinger](https://community.localwp.com/u/colegeissinger)\ **Post date:** [December 14, 2017, 1:28am UTC](https://community.localwp.com/t/updating-domain-name-to-local-ssl-not-verifying-now/4316/3 "2017-12-14T01:28:12Z")
Thanks @clay! #2 fixed the issue for me. So simple 😛 ---
**Author:** ![Qwik3r](https://avatars.discourse-cdn.com/v4/letter/q/bc8723/32.png) [@Qwik3r](https://community.localwp.com/u/Qwik3r)\ **Post date:** [May 9, 2018, 3:16am UTC](https://community.localwp.com/t/updating-domain-name-to-local-ssl-not-verifying-now/4316/4 "2018-05-09T03:16:44Z")
I did all of the above and still have the error in Chrome that the SSL is not trusted. Everything was working fine until I went from .dev to .local. Using local version 2.2.4 and chrome 65. ---
**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\ **Post date:** [May 16, 2018, 9:32pm UTC](https://community.localwp.com/t/updating-domain-name-to-local-ssl-not-verifying-now/4316/5 "2018-05-16T21:32:13Z")
@Qwik3r, Are you still experiencing this issue? Have you tried restarting your browser? Sometimes that’s what it takes to load in the newly trusted certificate. ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\ **Post date:** [August 25, 2020, 6:33pm UTC](https://community.localwp.com/t/updating-domain-name-to-local-ssl-not-verifying-now/4316/6 "2020-08-25T18:33:23Z")