# Email addresses being changed when pulling from Live to local
**URL:** https://community.kinsta.com/t/email-addresses-being-changed-when-pulling-from-live-to-local/2234
**Category:** Bug Reports
**Created:** [April 21, 2023, 2:41pm UTC](https://community.kinsta.com/t/email-addresses-being-changed-when-pulling-from-live-to-local/2234 "2023-04-21T14:41:10Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@jdgcss](https://community.kinsta.com/u/jdgcss)
#### Post date: [April 21, 2023, 2:41pm UTC](https://community.kinsta.com/t/email-addresses-being-changed-when-pulling-from-live-to-local/2234/1 "2023-04-21T14:41:10Z")
**Q: Date/Time this occurred (Provide your time zone also)**
**A:** Any time local site is pulled down
**Q: DevKinsta Version**
**A:** 2.10.0 (2.10.0.6571)
**Q: OS Version**
**A:** Max OSX 13.3.1 (22E261)
**Q: Docker Desktop Version**
**A:** 4.17.0 (99724)
**Q: Were any error codes or messages observed? If so, what were they?**
**A:** No
**Q: Detailed Description of the Problem**
**A:**
When copying from Live to local any email addresses are changed that contain the live domain. It’s similar to the behaviour mentioned here:
> [@All email addresses on site change when i pull a site to local or push up to production](https://community.kinsta.com/t/all-email-addresses-on-site-change-when-i-pull-a-site-to-local-or-push-up-to-production/941/1):
>
> When I pull our live site down locally to make changes, every email address on our site changes from the live version of the url to the local version of the URL. The same occurs when i push my local changes up to the live site. Is there any way I can make it so it does not change any email address in the content of our web pages when pushing and pulling? As an example it’s changing the address like this: from: [info@example.com](mailto:info@example.com) to: info@examplestagingsite.local We need to make sure the con…
However both me and my colleague (running the same setup) are finding email addresses are replaced in a way that includes the http protocol. These emails addresses are all stored in post meta table via the ACF pro plugin. Here are some screenshots:
**Live**
**Local**
---
### Author:  [@Alessandro](https://community.kinsta.com/u/Alessandro)
#### Post date: [April 21, 2023, 3:59pm UTC](https://community.kinsta.com/t/email-addresses-being-changed-when-pulling-from-live-to-local/2234/2 "2023-04-21T15:59:23Z")
Hi @jdgcss,
This is odd, when pulling a site from Kinsta, we grab the site URL and perform a search and replace only using that.
What do you see in your main.log file when looking for `[wpGetSiteUrl] Wp Site URL`? If you look for that string you should see the search and replace terms after a few lines. If you are not familiar with the main.log file location, you can find it by clicking on the question mark icon at the bottom left corner of DevKinsta and then on Reveal log file in File Manager.
Regards,
Alessandro
---
### Author:  [@jdgcss](https://community.kinsta.com/u/jdgcss)
#### Post date: [April 26, 2023, 1:49pm UTC](https://community.kinsta.com/t/email-addresses-being-changed-when-pulling-from-live-to-local/2234/3 "2023-04-26T13:49:51Z")
Hello @Alessandro - thanks for the reply. I;ve looked in the main.log and this is what’s there:
`[wpGetSiteUrl] Wp Site URL: https://coventryenergystorage.local [wpSearchAndReplace] Search and replace. Source: https://coventryenergystorage.local, to: https://coventryenergystorage.local `
That doesn’t look correct to me? I would have expected the Source value in search and replace to be the live website URL?
---
### Author:  [@Alessandro](https://community.kinsta.com/u/Alessandro)
#### Post date: [April 26, 2023, 3:18pm UTC](https://community.kinsta.com/t/email-addresses-being-changed-when-pulling-from-live-to-local/2234/4 "2023-04-26T15:18:16Z")
Hi @jdgcss,
depending on the process that DevKinsta is running yes, you can see a search and replace notification message that includes a source and destination domain that are the same. However, as you can see the search and replace includes https:// so it is unlikely that it has triggered the change reported in the first message of this thread. Is it possible that an additional search and replace has been done by using a plugin instead?