# Error: Could not connect to debugging client **URL:** \ **Category:** Application Support\ **Created:** [April 25, 2024, 12:29am UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343 "2024-04-25T00:29:36Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![natasha\_nightshift](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/natasha_nightshift/32/652_2.png) [@natasha\_nightshift](https://community.kinsta.com/u/natasha_nightshift)\ **Post date:** [April 25, 2024, 12:29am UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/1 "2024-04-25T00:29:36Z")
I cannot get my website to pull to my local machine. I have tried pulling from both local and staging. Typically when I pull from the staging website, a modal appears asking for my user credentials (a native Apple modal). Now when I pull, that modal does not appear, and eventually, it will just say ‘something bad happened’. When I check the `xdebug` file, it notes: `[381] [Step Debug] ERR: Could not connect to debugging client. Tried: host.docker.internal:9000 (through xdebug.client_host/xdebug.client_port) :-(` Can you kindly assist? ---
**Author:** ![Adrian\_L](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/adrian_l/32/2810_2.png) [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)\ **Post date:** [April 25, 2024, 2:18am UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/2 "2024-04-25T02:18:19Z")
Hi @natasha_nightshift 👋 I’m sorry to hear that you’re having trouble with our local deployment tool, Devkinsta. If you haven’t already, please close(quit) both the DevKinsta and Docker apps completely. And click on the “ **Re-apply configuratoin** ” if this warning comes up after re-launching the Docker Desktop app. ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/d/d93bb45e3a4e0238a17c2d03a4edf335355ad8e1.png) Then, reopen DevKinsta and try the ‘pull’ action again. If the issue persists, please send me a copy of your DevKinsta raw ‘main.log’ file via private message. To locate it, click the question mark icon at the bottom-left corner of DevKinsta and select the option “Reveal log file in File Manager”. We would like to take a closer look at why the Pull action is throwing such an error. ---
**Author:** ![natasha\_nightshift](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/natasha_nightshift/32/652_2.png) [@natasha\_nightshift](https://community.kinsta.com/u/natasha_nightshift)\ **Post date:** [April 25, 2024, 6:20pm UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/3 "2024-04-25T18:20:36Z")
Hi Adrian, 1. I quit DevKinsta and Docker 2. My Docker did not show me that error message. ![Screenshot 2024-04-25 at 2.20.25 PM](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/d/d01f08e464abb5b83e84ddad75532a2e1907d12f.jpeg) ---
**Author:** ![Adrian\_L](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/adrian_l/32/2810_2.png) [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)\ **Post date:** [April 25, 2024, 11:14pm UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/4 "2024-04-25T23:14:46Z")
Hi @natasha_nightshift Can you also send me a copy of your DevKinsta raw ‘main.log’ file via private message? We like to investigate further the cause of the error thrown by the Pull action. ---
**Author:** ![natasha\_nightshift](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/natasha_nightshift/32/652_2.png) [@natasha\_nightshift](https://community.kinsta.com/u/natasha_nightshift)\ **Post date:** [April 25, 2024, 11:31pm UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/6 "2024-04-25T23:31:07Z")
Sent to you privately! ---
**Author:** ![Adrian\_L](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/adrian_l/32/2810_2.png) [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)\ **Post date:** [April 26, 2024, 2:43am UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/7 "2024-04-26T02:43:10Z")
Hi @natasha_nightshift Thanks for sharing the main.log file. I reviewed the log, and I noticed several of these errors in the log file from different sites. It doesn’t look like the issue is specific to any one site. ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/2/2b14ce2d73e28249b57207faac7c1743304f5b3e.png) It’s possible that something went out of sync between Devkinsta and Docker. To fix this, I recommend that you first close the Devkinsta app and then delete all the Devkinsta containers in your Docker Desktop. Once you’ve done this, relaunch Devkinsta to re-generate those containers. Please note that deleting and recreating the containers should not result in the loss of your local site data, as it is stored in the Docker Volumes. However, if you don’t have any existing working local site running, it might be easier to just uninstall both Devkinsta and Docker and reinstall the apps to start fresh. I hope this information is helpful. Let us know how it goes. ---
**Author:** ![natasha\_nightshift](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/natasha_nightshift/32/652_2.png) [@natasha\_nightshift](https://community.kinsta.com/u/natasha_nightshift)\ **Post date:** [April 26, 2024, 2:09pm UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/9 "2024-04-26T14:09:34Z")
Hi Adrian, I deleted Kinsta, and Docker. I re-installed. Errors continue. The frustrating thing, is that I keep trying, alternating from pulling from staging and live and I just keep getting different errors. I resent you the log file and screenshots of the various errors. Error `DK0072` is particularly annoying because there are no `samename.conf files` as shown in the screenshot. `DK0029` just tells me to try again later and to report here… To clarify, the site in question is [nightshiftstudio.co](http://nightshiftstudio.co). AND I also tried on another computer entirely and same problem is occurring. Could this be a weird permission problem on the server? I typically get a modal that reads: `"DevKinsta wants to add domain to hosts file"`, in which I enter my password and the pull completes. This happens on every other site I pull, except for the `nightshiftstudio` project. ![Screenshot 2024-04-26 at 12.43.43 PM](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/3/333dd90c04ebd3b8f00d0b23c12ac21bb23b9900.png) ---
**Author:** ![Andrew](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/andrew/32/2792_2.png) [@Andrew](https://community.kinsta.com/u/Andrew)\ **Post date:** [April 26, 2024, 7:13pm UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/11 "2024-04-26T19:13:24Z")
Hi @natasha_nightshift! Thank you for your reply! After further reviewing the main.log file you shared it does appear for your [nightshiftstudio.co](http://nightshiftstudio.co) site there is a permissions related issue occurring during the rsync process. We would be happy to help ensure that all of the file/folder permissions are correct on your site so you may attempt to perform the import again. We would need you to open a support request with our team via a live chat in MyKinsta or by emailing [support@kinsta.com](mailto:support@kinsta.com) so we can perform this action in a verified support session. Once our team has helped with ensuring the file/folder permissions are correct you may try importing the site again into DevKinsta to see if that has helped resolve the problem. We look forward to hearing from you! Best regards ---
**Author:** ![natasha\_nightshift](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/natasha_nightshift/32/652_2.png) [@natasha\_nightshift](https://community.kinsta.com/u/natasha_nightshift)\ **Post date:** [April 26, 2024, 10:02pm UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/12 "2024-04-26T22:02:30Z")
I am confirming that it is now working. And that was indeed the problem. Thanks! ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/8/80f8c4e56fecc02327a0964e6bf63a716483529f.png) [@system](https://community.kinsta.com/u/system)\ **Post date:** [April 29, 2024, 10:03am UTC](https://community.kinsta.com/t/error-could-not-connect-to-debugging-client/3343/13 "2024-04-29T10:03:04Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.