# "This site can’t be reached" after cloning -- chrome automatic appends ".local" to the domain name **URL:** \ **Category:** Support\ **Created:** [August 4, 2024, 7:14pm UTC](https://community.localwp.com/t/this-site-can-t-be-reached-after-cloning-chrome-automatic-appends-local-to-the-domain-name/44035 "2024-08-04T19:14:11Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![rei2work](https://avatars.discourse-cdn.com/v4/letter/r/3be4f8/32.png) [@rei2work](https://community.localwp.com/u/rei2work)\ **Post date:** [August 4, 2024, 7:14pm UTC](https://community.localwp.com/t/this-site-can-t-be-reached-after-cloning-chrome-automatic-appends-local-to-the-domain-name/44035/1 "2024-08-04T19:14:11Z")
### What issue or error are you experiencing? ## “Open site” launches a site an alwyas append a “.local” as post fix, and the browser just says " This site can’t be reached". ### What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc ![image](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/a/b/ab3e05776c989b74badcd3f5f73e92696dbd94cf.png) * * * ### System Details - **Local Version:** - **Operating System (OS) and OS version:** * * * ### Local Logs Attach your Local Logs here ([Help Doc - Retrieving Local’s Log](https://localwp.com/help-docs/troubleshooting/retrieving-locals-log-file/)) * * * _ **Security Reminder** _ Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed. ---
**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\ **Post date:** [August 6, 2024, 2:10pm UTC](https://community.localwp.com/t/this-site-can-t-be-reached-after-cloning-chrome-automatic-appends-local-to-the-domain-name/44035/2 "2024-08-06T14:10:13Z")
Hi @rei2work The domain suffix is set in your Preferences under New Site Defaults. By default this is always going to be `.local`. You can change it to something else if you want however in that section indicated. After that if you have any other questions or concerns don’t hesitate to reach back out. ---
**Author:** ![rei2work](https://avatars.discourse-cdn.com/v4/letter/r/3be4f8/32.png) [@rei2work](https://community.localwp.com/u/rei2work)\ **Post date:** [August 7, 2024, 5:37am UTC](https://community.localwp.com/t/this-site-can-t-be-reached-after-cloning-chrome-automatic-appends-local-to-the-domain-name/44035/3 "2024-08-07T05:37:07Z")
Thank you that must be it!! I’ve “fixed” it the hard way (created a new site, and loaded a backup data of an older revision) but I’ll keep this solution in mind for next time.! ---
**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\ **Post date:** [August 7, 2024, 1:19pm UTC](https://community.localwp.com/t/this-site-can-t-be-reached-after-cloning-chrome-automatic-appends-local-to-the-domain-name/44035/4 "2024-08-07T13:19:15Z")
Sounds good @rei2work! 💚 ---
**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 9, 2024, 1:19am UTC](https://community.localwp.com/t/this-site-can-t-be-reached-after-cloning-chrome-automatic-appends-local-to-the-domain-name/44035/5 "2024-08-09T01:19:50Z")
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.