Unable to manage site locally, ERR_EMPTY_RESPONSE

DevKinsta Application Support
1

It worked fine last week for managing a site locally when I first set it up until yesterday when Docker started hanging on boot up. I implemented a solution that I found online which I believe involved setting up Ubuntu and switching to Linux containers from Windows. Everything loads and displays as normal, but attempting to open the site from DevKinsta gives an ERR_EMPTY_RESPONSE page.

I am using Windows 10 and have tried uninstalling and reinstalling both applications, purging data, and resetting to factory defaults. My main.log is attached. I’ve only just started learning WordPress.org and am already getting discouraged as to how I can manage my own site, so any assistance would be appreciated!

main.log (624.0 KB)

3

Hi @gnor :wave: Welcome to DevKinsta community!

I’ve checked your main.log file you sent and noticed there seems to be couple of errors related to your docker possibly (as you also mentioned in your post that the Docker stared hanging on boot up), something like these:

[2023-05-08 03:55:46.863] [error] create thumbnail error: Error: socket hang up
[2023-05-08 03:55:46.864] [info] [createThumbnail] Trying to create thumbnail, tries left: 4
[2023-05-08 03:55:49.868] [error] create thumbnail error: Error: socket hang up
[2023-05-08 03:55:49.869] [info] [createThumbnail] Trying to create thumbnail, tries left: 3
[2023-05-08 03:55:52.874] [error] create thumbnail error: Error: socket hang up
[2023-05-08 03:55:52.874] [info] [createThumbnail] Trying to create thumbnail, tries left: 2
[2023-05-08 03:55:55.879] [error] create thumbnail error: Error: socket hang up
[2023-05-08 03:55:55.879] [info] [createThumbnail] Trying to create thumbnail, tries left: 1
[2023-05-08 03:55:58.897] [error] create thumbnail error: Error: socket hang up
[2023-05-08 03:55:58.898] [error] [createThumbnail] Failed to create thumbnail on C:\Users\gnord\AppData\Roaming\DevKinsta\static\img\sites\dec31816-6ee5-4441-8fd1-f27ab77ba3a9.png, no more tries

[2023-05-08 03:56:10.333] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:56:13.731] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:56:20.349] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:56:23.735] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:56:30.363] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:56:33.743] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:56:40.379] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:56:43.756] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:56:50.393] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:56:53.760] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:00.402] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:03.765] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:10.412] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:13.768] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:20.415] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:23.783] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:30.431] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:33.794] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:40.433] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:43.804] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:50.439] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:57:53.807] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:58:00.440] [error] [watchDockerService] Pinging docker: FAILED. connect ENOENT //./pipe/docker_engine
[2023-05-08 03:58:00.441] [error] [watchDockerService] max retired exceeded. Pinging stopped.

I assume you don’t have any existing sites created in your DevKinsta yet?
if that so, then you may want to close and shutdown both DevKinsta and Docker Dekstop completely.

After that please remove and clean-up DevKinsta completely - remove/delete any folders and data related to it, for example, inside these folders:
C:\Users\gnord\AppData\Roaming\DevKinsta ,
and
C:\Users\gnord\DevKinsta .
Also please remove all containers, images, network volumes, etc. in your Docker Desktop.

Once they’re removed completely, please restart your computer, then you may want to re-install the Docker Desktop first, and once done, you can re-install DevKinsta (it will re-download/setup new images/containers from scratch). Then please try to create a new local site there and see if you can access that site?

If it’s still showing error, please re-send your new main.log file so we can double check (and please let us know your Windows 10 version, if it’s Home or Pro version? and if you use WSL2 or Hyper-V ?)

Regards,
Agus

4

Hi Agus,

I did have a site created, but it wasn’t being hosted online. It looks like the problem was specific to that site only for some reason. I was able to create and manage a new one without issue, though I couldn’t restore the old in an operable fashion.

It’s a recoverable loss, but I need to know how to avoid losing a whole site in the future. I’d like to practice on the local system before I start investing in a hosting sub. Does the ability to create a backup hinge on the subscription or I am able to retrieve it just from pushing to a Kinsta account?

Thanks

5

Thank you for your reply and confirmation gnor!

Glad to see you were able to create a new local site just fine! yeah if it worked, then most likely something with that specific previous site that might be the culprit (and I have no idea either how it was created/built and modified/edited/altered previously on your local computer :man_shrugging: that would be causing the error and how to restore/recover that old site in question. )

Got it! Yeah I do understand that we all always really want to avoid losing site’s data/files (or the whole site)!
There’s no such automated site backup function in DevKinsta, and in order to backup the local site that needs to be done manually on your computer.

You can make a copy of your local site’s files that are saved under this sub-folder (to be copied to somewhere else as a backup):
C:\Users\gnord\DevKinsta\public\the-site-name
(for example: C:\Users\gnord\DevKinsta\public\summary-web-solutions )
That site’s sub-folder contains your WordPress files (and sub-folders) used for that specific site.

Then you will also need to get a backup of that site’s data (which is stored in the database). You can use the Adminer database manager/tool to export your specific site’s database (to be exported/dumped into .sql file), then you can save that .sql database file as your site’s DB backup.

About the site backup/restore feature on our Managed WordPress hosting service, we automatically back up each site every day - each daily backup will be stored for 14 days. User can create up to 5 manual backups as well. Also user/you can download an archive file (.zip) containing your entire WordPress site (once per week).
More about this can be read here.

Regards,
Agus