# Dk0038 - Could not set WordPress config
**URL:** https://community.kinsta.com/t/dk0038-could-not-set-wordpress-config/3151
**Category:** Bug Reports
**Created:** [March 13, 2024, 2:25pm UTC](https://community.kinsta.com/t/dk0038-could-not-set-wordpress-config/3151 "2024-03-13T14:25:07Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@rejdr](https://community.kinsta.com/u/rejdr)
#### Post date: [March 13, 2024, 2:25pm UTC](https://community.kinsta.com/t/dk0038-could-not-set-wordpress-config/3151/1 "2024-03-13T14:25:07Z")
**Q: Date/Time this occurred (Provide your time zone also)**
**A:** Mar 13 - 10:18am EST
**Q: DevKinsta Version**
**A:** 2.13.1
**Q: OS Version**
**A:** Sonoma 14.4
**Q: Docker Desktop Version**
**A:** 4.27.2
**Q: Were any error codes or messages observed? If so, what were they?**
**A:** Dk0038
**Q: Detailed Description of the Problem**
**A:** Trying to import a site through DevKinsta, it gets stuck here with a DK0038 error. See screenshot below.
I was able to successfully import some of my other sites, two of my sites are giving me this error.
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [March 14, 2024, 12:15am UTC](https://community.kinsta.com/t/dk0038-could-not-set-wordpress-config/3151/2 "2024-03-14T00:15:14Z")
Hi @rejdr !
Could you kindly send me a copy of your **main.log** file through direct message? You can find it by clicking on the question mark icon at the bottom left corner of DevKinsta, and then selecting “ **Reveal log file in File Manager** ”. We would like to take a look at it and help identify the problem.
Thank you and regards.
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [March 14, 2024, 3:22am UTC](https://community.kinsta.com/t/dk0038-could-not-set-wordpress-config/3151/4 "2024-03-14T03:22:10Z")
@rejdr
I have reviewed the main.log file and noticed an error that says:
`2024-03-13 10:22:15.233] [error] Error - DK0038: SET_WP_CONFIG: Error (1): u[31;1mError:[0m Could not process the 'wp-config.php' transformation.Reason: Unable to locate placement anchor.`
This error usually means that DevKinsta is unable to locate the **wp-config.php** file in the default root directory ( **/public** ). After checking your website, I found that it is not configured as a standard WordPress installation due to its custom file structure, likely Bedrock.
I suggest you try the workaround provided in this thread to push through the import: [Import WordPress/Bedrock host on Kinsta to DevKinsta](https://community.kinsta.com/t/import-wordpress-bedrock-host-on-kinsta-to-devkinsta/1733)
Please let us know if you need further assistance.
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [March 15, 2024, 2:35am UTC](https://community.kinsta.com/t/dk0038-could-not-set-wordpress-config/3151/6 "2024-03-15T02:35:04Z")
@rejdr
I hope the following information helps clear your questions in our DM. 🙂
1. When pulling a site (live or staging) to Devkinsta, it doesn’t have any effect on the source Kinsta site.
2. I haven’t had a chance to set up a Bedrock site for testing yet. However, theoretically, if you create a copy of your wp-config.php file to the **/public** directory and add the appropriate database connection strings inside the config file, you should be able to perform a **Pull to DevKinsta**. If the pull is successful, then the **Push to Kinsta** should also work. Nevertheless, I recommend that you first back up your Staging/Live site (whichever is the destination site for the **Push to Kinsta** ) before proceeding.
- Also please note that you will also need to manually update the document root path in the Nginx editor from **www/kinsta/public/yoursite** to **www/kinsta/public/yoursite/web** in DevKinsta.
1. When pushing to Kinsta, DevKinsta will give you the option to push only files, database, or both.
Best,