# Can't connect to site from computer where I built site using Local

**URL:** https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578
**Category:** Support
**Created:** [July 21, 2022, 6:53pm UTC](https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578 "2022-07-21T18:53:41Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![syndicat](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@syndicat](https://community.localwp.com/u/syndicat)
#### Post date: [July 21, 2022, 6:53pm UTC](https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578/1 "2022-07-21T18:53:41Z")

</div>

Others can see site but I can’t connect using the computer I used to build the site using Local. Site was successfully migrated to a hosting company’s servers and others can see the site. But from my computer browsers all say “can’t connect.”

Since I built the site on this computer, is there some residual Local created code that doesn’t allow this computer to seek the URL on the net? How do I enable this computer to connect to the site on the hosting company’s servers?

I’ve emptied my cache and rebooted my router and that has not solved the problem. I’ve tried three different browsers (Chrome, Microsoft Edge, and Firefox). Same problem.

---

<div class="post-metadata">

### Author: ![syndicat](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@syndicat](https://community.localwp.com/u/syndicat)
#### Post date: [July 22, 2022, 4:11pm UTC](https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578/2 "2022-07-22T16:11:42Z")

</div>

The problem here was caused by Local modifying the hosts file. Local adds a line resolving the site URL to localhost. Thus preventing browsers from going out onto the internet to search for that URL.

---

<div class="post-metadata">

### Author: ![sambrockway](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/sambrockway/32/18726_2.png) [@sambrockway](https://community.localwp.com/u/sambrockway)
#### Post date: [July 25, 2022, 10:43am UTC](https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578/3 "2022-07-25T10:43:05Z")

</div>

Hi @syndicat - thank you for your question & follow up.

Is your problem solved or did you still need some support here?

Thank you!

Sam 👩🏼‍💻

---

<div class="post-metadata">

### Author: ![WPSuperheroes](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/wpsuperheroes/32/16534_2.png) [@WPSuperheroes](https://community.localwp.com/u/WPSuperheroes)
#### Post date: [September 13, 2022, 8:06am UTC](https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578/4 "2022-09-13T08:06:26Z")

</div>

I have this SAME Issue. Where is the localwp hosts file?  
I can’t connect to a LIVE site, and I HAVE NOT pulled a local version.

The hosts file at /private/etc/hosts does not list the LIVE sites domains.  
I do have ALL these sites at WPEngine.

If I knew where the hosts file is, I could fix this, but it’s not in the expected location.  
Your support is appreciated.

---

<div class="post-metadata">

### Author: ![syndicat](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@syndicat](https://community.localwp.com/u/syndicat)
#### Post date: [September 13, 2022, 3:25pm UTC](https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578/5 "2022-09-13T15:25:17Z")

</div>

yes. the problem was the hosts file. local had identified my ULR with localhost.

tomw

---

<div class="post-metadata">

### Author: ![WPSuperheroes](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/wpsuperheroes/32/16534_2.png) [@WPSuperheroes](https://community.localwp.com/u/WPSuperheroes)
#### Post date: [September 13, 2022, 9:27pm UTC](https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578/6 "2022-09-13T21:27:13Z")

</div>

The weird part is I can’t access ANY of my sites on WP Engine.  
And I only pulled 1 site to develop locally.

The hosts file does not list ALL of my WP Engine sites, it only lists the 1 site.  
But I can’t access 22 other websites I have at WP Engine.

Everyone else has one site they are deving on. But I’m the Hosting Account owner, and I cannot access 22 other sites.

Your assistance is much appreciated.  
How do I fix this?

---

<div class="post-metadata">

### Author: ![RIF-Kiwi](https://avatars.discourse-cdn.com/v4/letter/r/3d9bf3/32.png) [@RIF-Kiwi](https://community.localwp.com/u/RIF-Kiwi)
#### Post date: [September 14, 2022, 5:55am UTC](https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578/7 "2022-09-14T05:55:16Z")

</div>

Hi, I have a similar problem. I can log onto Local, and can open the site I built. BUT, when I try to access WP Admin, the local site does not accept my local WP credentials to log onto the dashboard. I know the login details are correct as they are saved in a Password Safe (LastPass). I also tried to login using my email address but that was not recognised either. I’ll attach a screenshot of my local dashboard in case that suggests something to readers? I have been able to access the dashboard in the past, so I am wondering what is happening? I did update local today for the latest version. Might that have caused it? Thanks, Roger.

 ![Screenshot 2022-09-14 175346](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/d/2/d22331b8cd3cab7bc3beeb0142dbe762e7b103a9.png)

---

<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: [December 13, 2022, 5:56am UTC](https://community.localwp.com/t/cant-connect-to-site-from-computer-where-i-built-site-using-local/32578/8 "2022-12-13T05:56:12Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
