DevKinsta install error

DK0001

Description: Not enough gratis deejay infinite.

During certain actions (DevKinsta installation, site creation, site import from MyKinsta, etc.), DevKinsta checks the currently available disk space. If at that place is non enough deejay space on your local machine, you lot will see this error.

Solution

Free up disk space on your computer, and echo the activeness that caused the initial fault.

DK0002

Description: At that place is no internet connexion.

During certain actions (DevKinsta installation, site import from MyKinsta, etc.), DevKinsta checks for a stable Cyberspace connection. If your local automobile is non connected to the Internet, you will meet this error.

Solution

Ensure your computer is continued to the Cyberspace, and repeat the action that acquired the initial fault.

DK0003

Description: Couldn't install Docker.

DevKinsta couldn't install Docker Desktop.

Solution

Ensure your estimator is adjustment to organisation requirements and attempt to install Docker Desktop manually. After y'all finished the Docker Desktop installation, endeavour to restart DevKinsta.

DK0004

Description: Couldn't start Docker. Please try to offset Docker manually.

DevKinsta couldn't start Docker Desktop.

Solution

Please attempt to start Docker Desktop manually and after that restart DevKinsta.

DK0005

Description: Couldn't create docker containers.

DevKinsta couldn't create Docker containers.

Solution

Restart Docker Desktop manually and later that, restart DevKinsta.

DK0006

Description: Couldn't download docker images.

DevKinsta couldn't load the required Docker images.

Solution

Please cheque your net connection. If it is stable, delight endeavour to restart DevKinsta.

DK0007

Description: Couldn't download Docker.

DevKinsta couldn't download Docker Desktop.

Solution

First, check your internet connection. If it is stable, please endeavour to restart DevKinsta.

DK0008

Clarification: Couldn't fetch IP.

DevKinsta couldn't discover Docker's IP address.

Solution

Please attempt to restart Docker Desktop manually, and later that, restart DevKinsta.

DK0009

Description: Tin't first docker container

DevKinsta couldn't commencement Docker containers.

Solution

Please try to stop DevKinsta related Docker containers, and after that, restart DevKinsta.

          docker kill devkinsta_fpm && docker impale devkinsta_nginx && docker kill devkinsta_adminer && docker kill devkinsta_db && docker impale devkinsta_mailhog

DK0010

Description: Couldn't load docker images.

DevKinsta couldn't load the required Docker images.

Solution

Please cheque your net connection. If information technology is stable, please try to restart DevKinsta.

DK0011

Description: Unknown server error occurred. Please endeavor it once again.

You lot may run into this mistake if DevKinsta is unable to the Kinsta API.

Solution

First, check your Internet connection to come across if there are any issues. If non, effort again later in case the event is on the MyKinsta API side.

DK0012

Clarification: Your request timed out. Please try it over again.

You may see this error if DevKinsta is unable to the Kinsta API due to a timeout.

Solution

Commencement, check your Internet connexion to see if at that place are whatsoever issues. If non, try over again after in case the upshot is on the MyKinsta API side.

DK0013

Description: Remote server received wrong data. Please endeavor it again.

You lot may come across this error if DevKinsta receives a bad request error from the Kinsta API.

Solution

Delight report this error to the DevKinsta Community Forum.

DK0014

Description: You are unauthenticated. Please endeavor to re-login into MyKinsta account.

You may see this error if DevKinsta receives an unauthorized request fault from the Kinsta API.

Solution

Go to the DevKinsta setting pages, and try logging in to your MyKinsta account again. Afterwards, retry the process.

DK0015

Clarification: You lot don't have permission for this action.

Y'all may see this error if DevKinsta encounters a MyKinsta permissions fault when accessing the Kinsta API.

Solution

Go to your MyKinsta profile, and ensure you take the necessary site permissions.

DK0016

Description: Couldn't find remote server. Please attempt information technology over again.

You may meet this error if DevKinsta receives a 404 error from the Kinsta API.

Solution

Please study this mistake to the DevKinsta Community Forum.

DK0017

Description: You fabricated besides many requests. Please try it again a few minutes later.

Yous may see this error if DevKinsta encounters a "besides many requests" error from the Kinsta API. This fault occurs when the Kinsta API is chosen too frequently.

Solution

Expect a few minutes, and effort the activeness again.

DK0018

Clarification: You didn't grant permission for site deletion.

Yous may run into this error if DevKinsta is unable to delete a site due to incorrect permissions to perform the deletion activity.

Solution

Windows macOS
Try to delete the site again, and approve the Windows confirmation dialog. Endeavor to delete the site again, and provide your correct countersign when prompted past macOS.

DK0019

Clarification: NGINX configuration failed

You may come across this error if DevKinsta is unable to update the Nginx configuration file.

Solution

First, effort restarting DevKinsta and recreating the site. If that does non work, check the sites.ini file in your projectFolder/kinsta folder with a text editor, and remove any duplicate entries.

DK0020

Description: Database creation failed

Y'all may see this error if DevKinsta is unable to create the MySQL database. The database name is derived from the site name. This mistake occurs if the database proper noun is not valid.

Solution

Effort to recreate the site with a different proper name. If that does not work, try restarting DevKinsta.

DK0021

Description: WordPress site setup failed

Y'all may run across this mistake if DevKinsta is unable to install WordPress.

Solution

Try to restart DevKinsta, and recreating the site.

DK0022

Clarification: Host file update failed

During site creation, DevKinsta couldn't update the hosts file. You may see this error if DevKinsta is unable to update the computer's hosts file.

Solution

Windows macOS
Try recreating the site, and corroborate the Windows confirmation dialog. Effort recreating the site, and provide your right password when prompted by macOS.

DK0023

Description: Tin't add together certificate to Keychain

Y'all may run into this mistake if DevKinsta is unable the shop the security certificate in the macOS Keychain.

Solution

Endeavor to recreate the site, and ensure you provide the correct password to the macOS dialog prompt.

DK0024

Description: Can't write to Certificate shop

Y'all may see this error if DevKinsta is unable to store the security document in the Windows certificate manager.

Solution

DevKinsta needs to be run in Administrator way for the certificate to exist created. Endeavour to recreate the site, and ensure you provide the correct password to the Windows confirmation dialog.

DK0025

Description: Can't download site

Y'all may see this error if DevKinsta is unable to pull a site from Kinsta.

Solution

Restart DevKinsta, log in to your MyKinsta account in DevKinsta settings and endeavor to pull the site again.

DK0026

Clarification: Site push failed

Yous may see this mistake if DevKinsta is unable to push a site from Kinsta.

Solution

Restart DevKinsta, log in to your MyKinsta account in DevKinsta settings and endeavor to push button the site again. If the issue continues, check the application log file (master.log). Searching for the error lawmaking (DK0026) in the log file tin assist narrow down the search and may pb to some more than detailed data on the root crusade.

If the mistake persists, please report this error to the DevKinsta Community Forum.

DK0027

Description: Missing host file entry

You may run across this error if at that place is a missing hosts file entry. In this case, you won't be able to open this site via domain proper name.

Solution

Click on the Ready this push.

DK0028

Clarification: You didn't grant permission for edit the host file.

You may see this error if you lot don't grant permission for the hosts file modification.

Solution

Retry the process and provide the required permission.

DK0029

Clarification: Can't create mysql dump

You may see this error if, during site pull, DevKinsta is unable to create a MySQL dump on the remote server.

Solution

Try it over again later. If it still doesn't help, please study this error to the DevKinsta Customs Forum.

DK0030

Description: OPERATION INTERRUPTED

You lot may see this error if you close DevKinsta during site creation.

Solution

Click on the Retry button. If DevKinsta cannot recreate the site, delight endeavour to delete and recreate the site.

DK0031

Description: Port 80 or 443 is used.

Y'all may see this fault if port 80 is used.

Solution

Please attempt to close the process which is using port 80.

discover & impale process on macOS

          # find & kill processes which are using port lxxx sudo lsof -i tcp:80 | grep Listen | awk '{impress $two}' | xargs impale -ix

find & kill process on Windows

          # observe processes which are using port fourscore netstat -ano | findstr :80  # kill process by PID. supervene upon "<PID>" with result from the in a higher place command. taskkill /PID <PID> /F

DK0032

Description

You lot may see this fault on Windows if WSL2 is not installed or enabled.

Solution

Restart DevKinsta to initiate the WSL2 installation automatically. If DevKinsta is unable to install WSL2, yous can download information technology directly from Microsoft every bit well.

DK0033

Description: Can't connect to database

This error occurs when DevKinsta is unable to connect to the MySQL database.

Solution

Follow the steps below to resolve this mistake.

  1. Export your site'southward database with Adminer. (optional)
  2. Close DevKinsta.
  3. Run this control in terminal – docker container rm devkinsta_db && docker volume rm devkinsta_db_data.
  4. Start DevKinsta.
  5. Import the database with Adminer. (optional)

DK0034

Clarification: Please restart your computer to finish installation.

This error occurs when a reckoner restart is required.

Solution

Restart the computer and launch DevKinsta.

DK0035

Description

This error occurs on Windows if DevKinsta is unable to download WSL2 during the installation procedure.

Solution

Restart DevKinsta to commencement the WSL2 download again.

DK0036

Description

This error occurs if the Windows Subsystem for Linux (WSL2) feature is not enabled.

Solution

Enable WSL2 by following Microsoft's documentation.

DK0037

Description: Container not constitute

This fault can occur because the Docker container doesn't exist.

Subscribe At present

Solution

Follow any instructions provided in the mistake message. If instructions are not provided or practice non resolve the error, restart DevKinsta.

DK0038

Description: Prepare WP config

This mistake occurs when the wp-config.php file is missing or misconfigured.

Solution

Click on the Retry button shown in DevKinsta.

DK0039

Description: Docker stops mutual

If Docker stops and DevKinsta can't communicate with it, this error is shown.

Solution

Restart Docker Desktop manually, and after that, restart DevKinsta.

DK0040

Description: Could non renew the ssh key.

Yous may see this error when DevKinsta tries to renew the ssh cardinal during site import.

Solution

Outset, cheque your Internet connection to meet if in that location are any issues. If non, endeavour again later in instance the issue is on the MyKinsta API side.

DK0044

Description: Tin't write to Document store

Y'all may see this error when DevKinsta tries to create a local certificate on the organization for your site.

Solution

Endeavor to recreate the site, and ensure you provide the correct countersign to the Linux dialog prompt.

DK0045

Description: Certificate is non verified

You may see this error when DevKinsta tries to create a local certificate but the verification process fails due to an already existing or certificate in the database.

Solution

For advanced users: try to find and manually delete the corresponding certificates from your database located at "home/yourusername/.pki/nssdb/cert9.db"

DK0046

Description: Failed to install certutil package

You lot may see this error when DevKinsta tries to install missing packages that are necessary to create and manage certificates on your Linux system.

Solution

Open a concluding window and run sudo apt update, and so retry the SSL creation in DevKinsta. You can too try to manually install the necessary packages past running sudo apt install libnss3-tools or combining to two commands and run sudo apt update && apt install libnss3-tools. To check whether the install was successful, run certutil in the terminal and check the output.

DK0047

Description: DevKinsta couldn't overwrite sites.ini. Site creation is failed.

You may see this error when DevKinsta wants to overwrite the sites.ini file in your DevKinsta root Folder.

Solution

Go to your root DevKinsta folder and go to the kinsta folder. Delete the sites.ini file and so start DevKinsta.

DK0048

Clarification: You don't have the necessary privileges to outset the Docker client. Please set the required permissions and try once again.

You may see this error if you use Linux and the Docker client does not have the necessary privileges or permissions to showtime on your system.

Solution

You need to check your user profile to be sure that you lot have the necessary permissions to run the docker client.

To temporarily give the permissions to your user profile (for the current session only), run sudo chmod 666 /var/run/docker.sock in final, then click on the Retry button in DevKinsta to continue the startup process.

If yous want to fix the permissions permanently (recommended), add together your user profile to the docker grouping by following the steps below.

  1. Make sure that the docker group exists by running sudo groupadd docker in terminal.
  2. Next, run the groups command to check if your user is added to the docker group.
  3. If y'all demand to add your user to the docker group, run sudo usermod -aG docker $USER.
  4. Run sudo chmod 666 /var/run/docker.sock to set the permission.
  5. Log in and log out in order for the changes to take result.

DK0049

Description: Could not delete site'due south content.

Y'all may see this error if the devkinsta_nginx docker container is non running while you are trying to delete a site's content.

Solution

Make sure that devkinsta_nginx is running and try again.

DK0050

Description: Could not delete site entry from sites.ini.

You lot may run across this error if the devkinsta_nginx docker container is not running while y'all are trying to delete the site's entry from the sites.ini file.

Solution

Make sure that devkinsta_nginx is running and endeavor once more.

DK0051

Description: Could not delete the database.

Y'all may see this fault when the site'southward database cannot be deleted due to internal bug.

Solution

You can effort to manually delete the database using the CLI past running docker exec devkinsta_db bin/sh -c 'mysql -u root -p[YOUR_DB_PASSWORD] -e "driblet database [YOUR_SITE];"' in terminal.

You tin cheque whether the database has been deleted or non by running docker exec devkinsta_db bin/sh -c 'mysql -u root -p[YOUR_DB_PASSWORD] -east "show databases;"' in last.

DK0052

Description: Could not salvage php.ini content

You lot may see this mistake if the devkinsta_fpm container is not running when trying to save your changes in the php.ini editor.

Solution

Make certain that the devkinsta_fpm container is up and running and try once more.

DK0053

Description: Could not relieve php.ini content

You may see this error if the devkinsta_fpm container failed to restart after updating the php.ini file.

Solution

In case clicking on the Retry button does non assistance, you tin either endeavor to offset the container manually or restart DevKinsta.

DK0054

Clarification: Could not update sites.ini with the new ports.

Y'all may see this fault if the devkinsta_nginx container is not running while you are trying to update the sites.ini file with the new ports you selected.

Solution

Brand certain that the devkinsta_nginx container is running and try again.

DK0055

Description: Could not recreate Nginx container with new ports.

You may see this error when DevKinsta is non able to recreate the devkinsta_nginx container on the new ports you selected.

Solution

If clicking on the retry button does not help, you tin can either try to relaunch DevKinsta or recreate the devkinsta_nginx container yourself using the docker CLI.

For example, to create the container on ports eighty and 443 on macOS, and Linux, you lot can run the following in terminal, replacing or setting the ${LATEST_IMAGE_VERSION} variable with the latest version of our DevKinsta Docker image:

docker run --network devkinst_network --name devkinsta_nginx \\
-p eighty:lxxx -p 443:443 \\
-v "[YOUR_HOME_PATH]/kinsta:/kinsta" \\
-5 "[YOUR_HOME_PATH]/logs:/www/kinsta/logs" \\
-five "[YOUR_HOME_PATH]/private:/world wide web/kinsta/private" \\
-five "[YOUR_HOME_PATH]/public:/www/kinsta/public" \\
-5 "[YOUR_HOME_PATH]/ssl:/www/kinsta/ssl" \\
-d kinsta/devkinsta_nginx:${LATEST_IMAGE_VERSION} \\

On Windows, you can use the aforementioned command without the linebreaks and the \\ separators.

To get the latest version of our images, run: docker image ls --filter=reference='kinsta/devkinsta_*'

DK0056

Clarification: Could not update site URLs with new ports.

You may see this fault if devkinsta_fpm is not running while trying to rename the site'southward URLs after y'all selected the new ports.

Solution

Brand sure that devkinsta_nginx and devkinsta_fpm containers are up and running.

DK0057

Clarification: We cannot brandish emails on computers with M1 fleck.

Currently, our mail service used past DevKinsta doesn't back up M1 chips.

Solution

Use a different figurer that doesn't have an M1 chip to check emails for your DevKinsta site.

DK0058

Description: Failed to re-create the site folder.

DevKinsta could not re-create the files to the new folder when renaming the folio.

Solution

Go to the DevKinsta/public binder. Delete the binder with the new site name and retry the renaming process in DevKinsta.

DK0059

Description: Failed to copy the database.

DevKinsta could not copy the database during site renaming.

Solution

Delete the newly created site's database and retry the renaming procedure in DevKinsta.

DK0060

Description: Failed to update the database.

DevKinsta was unable to update the URLs, domains, and emails in the new site database when renaming the site.

Solution

Check if the database exists. If not, try to create it manually and copy the old site data.

DK0061

Description: Failed to delete the sometime site's data.

You may see this mistake when DevKinsta tries to delete the old site's data.

Solution

Retry the site renaming and ensure you provide the correct password.

DK0062

Clarification: Failed to add certification to the store.

You may see this fault when DevKinsta tries to create a local document on the organisation for your site.

Solution

Retry the site renaming and ensure you provide the correct countersign. DevKinsta needs to exist in Ambassador mode on Windows.

DK0063

Description: Failed to restart a docker container

You may run across this mistake when DevKinsta failed to restart a docker container.

Solution

You tin can restart the container manually in Docker Desktop or in terminal (replace <container> with the container proper name):

          docker offset <container>

DK0064

Description: Couldn't remove remote files.

You may meet this error when something changes in your remote environment that makes DevKinsta unable to perform the file deletion command (rm) on the remote site's file system.

Such changes may exist:

  • Permission changes (DevKinsta does not accept permission to remove some files)
  • Folder structure changes (name of the remote site'due south root binder has changed since the pull).

Solution

Try to pull the remote site again and utilize the changes on the new site (east.g. copy and paste the modified files or database), then endeavor to push again. If that doesn't help, try logging out and logging back in over again.

If the mistake persists, check the application log file (main.log). Searching for the error lawmaking (DK0064) in the log file can help narrow down the search and may pb to some more detailed information on the root crusade.

DK0065

Description: Failed to upload local files

This mistake occurs whenever something is wrong with uploading the local site to the remote server (your MyKinsta environment'southward binder). This can be acquired by a failed connection to the remote server or unpredictable issues related to the uploaded files.

Notation that this step uses rsync as a tool to share files with the remote site, so anything that tin can crusade rsync to fail tin be the root cause of this consequence.

Solution

Try logging out of MyKinsta in DevKinsta, and and then log back in. If it nonetheless doesn't work, effort to pull the remote site again and apply the changes on the new site (e.g. copy and paste the modified files or database), then try to push button over again.

If the mistake persists, check the application log file (primary.log). Searching for the error code (DK0065) in the log file tin can aid narrow down the search and may lead to some more detailed information on the root cause. If that search doesn't bear witness any useful data, then try searching for rsync.

DK0066

Description: Failed to import database dump

This mistake means that DevKinsta was unable to import the local database dump into your MyKinsta site's database.

Possible root causes:

  • Local database dump was non created (very unlikely, because it would fail on Create MySQL dump step).
  • Your remote database does not exist or is down for some reason

Solution

Investigate your MyKinsta site's database and file organization to see if your database is working properly. If non, so there is an issue on the server side and our Back up team tin can help with this.

If your site's database is working properly, then there was likely an issue on DevKinsta side. Investigating the application log file (master.log) may be helpful. Searching for the error code (DK0066) in the log file can help narrow downwardly the search and may lead to some more detailed information on the root crusade.

DK0067

Description: Failed to run search and replace

Search and replace is a WordPress control that makes it possible to replace all occurrences of a string in the site's database. We use it to overwrite the local site'south URL with the remote site's original URL (to keep the site attainable after the push).

If the step is not functioning properly, so ii things may be wrong:

  • WordPress CLI is not bachelor or working in your site's folder on the remote server (MyKinsta)
  • Your remote database is downward

Solution

Check to see if WordPress CLI is working on your remote (MyKinsta) site. If WP CLI works but reports database-related issues, then your site is not connecting to the database properly. Review the database settings in your site'south wp-config.php file and ostend the database details are right.

If your remote database is down, contact our Support team to help resolve that upshot.

If the solutions suggested higher up practise not resolve the issue, then restoring a recent backup is recommended.

DK0070

Description: Failed to delete DNS record.

Couldn't delete a site'south URL from the DNS server of the FPM container.

Solution

Yous tin can delete manually it manually (supersede http://example.com with the URL you want to delete):

docker exec devkinsta_fpm dns_server delete -d http://case.com

DK0071

Description: Failed to add DNS record.

Couldn't add a site'south URL to the DNS server of the FPM container.

Solution

Endeavour to restart DevKinsta and click the Retry push. The DNS record should be created during the startup process.

DK0072

Description: Could not delete site config file

This mistake occurs when yous try to delete or rename a site but DevKinsta cannot delete the sitename.conf file stored in DevKinsta/nginx_sites.

Solution

The almost common reason this happens is due to permission bug, then you may need to manually delete the file.

DK0073

Description: Could not restart Nginx service

When a site is created, renamed, or deleted, the Nginx service needs to be restarted. This error appears if the restart fails.

Solution

To restart the Nginx container manually, open a concluding window and run the post-obit:

          docker terminate devkinsta_nginx docker start devkinsta_nginx

Checking Nginx logs or DevKinsta logs may provide more than details every bit to why the restart failed.

DK0074

Description: Failed to create site backup.

The site backup is an archived (zipped) version of a site in the temp folder on your local computer. This fault is rare and occurs but in edge cases such as running out of deejay space or incorrect permissions on the temp folder.

Solution

Review permissions for your temp binder and check to make certain at that place is enough space on the disk, especially in the example of larger sites.

DK0075

Description: Failed to restore the site backup.

Restoration can fail if the site'due south folder is not writeable for some reason. Another reason for failure tin be that the zip cosmos was non successful when creating the backup.

Solution

  1. Check if the site backup exists in the temp folder.
  2. If the backup exists, and then it can be manually extracted into the site's folder.

To help prevent this event, sync the site regularly to MyKinsta or apply a version control organisation such as Git to runway changes and allow you to restore from previous versions.