# Can't access Local site after cloning

**URL:** <https://community.localwp.com/t/cant-access-local-site-after-cloning/4599>\
**Category:** Support\
**Created:** [December 29, 2017, 8:48pm UTC](https://community.localwp.com/t/cant-access-local-site-after-cloning/4599 "2017-12-29T20:48:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![micahbdavis](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/micahbdavis/32/5360_2.png) [@micahbdavis](https://community.localwp.com/u/micahbdavis)\
**Post date:** [December 29, 2017, 8:48pm UTC](https://community.localwp.com/t/cant-access-local-site-after-cloning/4599/1 "2017-12-29T20:48:03Z")

</div>

Hi there.

I’ve been using Local with just one website (with site domain of ‘look-new.dev’) and it’s been great.

I just cloned my website, and when I try to access the original website via its Site Domain, the browser can no longer find it. I can only access it using the Live Link.

The new website clone was reachable. I tried deleting the new website clone, wondering if the original website would become accessible via the domain, but it didn’t help, and the original website is still unreachable via the site domain.

Thanks for the help.

---

<div class="post-metadata">

**Author:** ![chrisfly](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/chrisfly/32/2454_2.png) [@chrisfly](https://community.localwp.com/u/chrisfly)\
**Post date:** [December 30, 2017, 3:15pm UTC](https://community.localwp.com/t/cant-access-local-site-after-cloning/4599/2 "2017-12-30T15:15:06Z")

</div>

Hi @micahbdavis ,

happy to try and help here!

My first guess would be it relates to this issue:

> [@Change default domain suffix for new sites from .dev to .test](https://community.localwp.com/t/change-default-domain-suffix-for-new-sites-from-dev-to-test/2916/1):
>
> Google Chrome is soon going to implement a feature whereby all requests to .dev domains will be automatically redirected to https. This is because the .dev gTLD is owned by Google.
> 
> As recommended in that article, I think that Local should therefore not use .dev as the default extension for new sites, but use .test instead because .test is reserved for testing and development purposes.

and to resolve this, you may be able to do this:

> [@.dev domain doesn't work](https://community.localwp.com/t/dev-domain-doesnt-work/4277/3):
>
> Local’s default TLD is .local as of Local 2.1.0+. You can change existing sites with .dev over to .local (or any other TLD that you wish) by using the “Change Domain” button found under the “Setup” tab for each site.

Please give this a try and let me know how you get on.

Thanks,  
Chris 🙂

---

<div class="post-metadata">

**Author:** ![micahbdavis](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/micahbdavis/32/5360_2.png) [@micahbdavis](https://community.localwp.com/u/micahbdavis)\
**Post date:** [December 30, 2017, 4:13pm UTC](https://community.localwp.com/t/cant-access-local-site-after-cloning/4599/3 "2017-12-30T16:13:06Z")

</div>

That was it. Changing to .local took was the ticket.

Thanks. 🙏

---

<div class="post-metadata">

**Author:** ![chrisfly](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/chrisfly/32/2454_2.png) [@chrisfly](https://community.localwp.com/u/chrisfly)\
**Post date:** [January 2, 2018, 1:33pm UTC](https://community.localwp.com/t/cant-access-local-site-after-cloning/4599/4 "2018-01-02T13:33:14Z")

</div>

Glad to hear it @micahbdavis

If there is anything else, please do let us know.

---

<div class="post-metadata">

**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/cant-access-local-site-after-cloning/4599/5 "2020-08-25T18:33:30Z")

</div>