Cache Issue

What issue or error are you experiencing?

i set up a local WordPress environment using local by flywheel with same domain name that i have on live server now my live site is not accessable from my laptop if local by flywheel is on it will go on local domain but if local by flywheel is off it will show This site can’t be reached


What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

I clear browser cache and system cache


System Details

  • Local Version:

local-7.2.1-windows

  • Operating System (OS) and OS version:
    Windows 10 Pro

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)


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.

1 Like

Hi @Hamza-Najam

The domain in your Local app should not match the domain of the live site. This is intentional to avoid the problems you’re running into. When you push/pull the site there will be search and replaces that happen automatically to change the domain.

It might be easiest to just wipe the site from your Local install and then reimport it but allow the domain name to remain how it is named in the app.

1 Like

Hi Nick,

What you are saying isn’t intuitive – in other words, one wouldn’t just assume what you described to be the case, so it must be documented somewhere right? Can you put a link to where in LocalWP documentation it states that your local site can’t be named the same as your live site? Thanks.

Sorry for any confusion here. To clarify what I mean is that if your live site domain is CodeSlayer2010.com you wouldn’t want to change your Local site to the same. You could still use CodeSlayer2010 but it would end in .local instead of .com. Unless you’re using Localhost as your Router Mode in which case it would be something like localhost:10005. Sometimes users will try and edit these domains to match and run into redirect/caching issues naturally. Reading back over the original post I’m not 100% sure if that is what happened here but that’s what I assumed.

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