No response in procesbars DevKinsta

It is a bit faster this time. But I’m getting this error.

Resulting in not downloading it anymore

Please leave it as it is and send via DM the latest main.log file

Regards,
Alessandro

This is it, but I already started the “opnieuw proberen” button. Because I read the message too late.

We just experiencing the same problem:

I can share my log again via PM

Please delete the main.log file, then click the retry button and send the new copy of the log that gets created once the process fails again

We’ve shared the new fresh main.log file. Same error occurs.

Thank you for the log @NP_vision we’ll review it and give you an update here.

Regards,
Alessandro

Do you have any updates?

Not yet I am afraid, our devs are still looking into the possible causes.

Regards,
Alessandro

We are still waiting. Can you give us an update?

Hello @NP_vision ,
our developers are still looking into the issue. Unfortunately without being able to reproduce the issue on this side, troubleshooting this kind of error is not easy.

If you want to try a workaround in the meantime, you can access your site in MyKinsta, move to the Backups page, and request a downloadable backup. Once the backup is ready you can download a copy of your site as .zip folder and import it manually in DevKinsta.
You can follow this guide on how to import the .zip backup

Regards,
Alessandro.

Hello NP,

We’ve got an update from 1 of our developers, and he suggested to run the following command line (on your Mac terminal) as a workaround to perform the site’s files transfer (via rsyc ) from your hosting account on Kinsta server to your local site’s folder on your computer/Mac :

docker run --rm -i \
  -v "/home/USERNAME/DevKinsta/public/THESITENAME":/target \
  -v "devkinsta_ssh":/tmp/.ssh \
  kinsta/devkinsta_rsync-ssh:1.3.0 \
  rsync --delete --timeout=60 -rz -L -e "ssh -p SSHPORT -o 'StrictHostKeyChecking no'" --info=progress2 --no-i-r SSHUSERNAME@REMOTEHOSTIP:/www/SITEUSERNAME/public/. /target/

Note:

  • Replace the USERNAME with your actual user name used on your local computer/Mac

  • Replace the THESITENAME with your actual site name used on your local computer/Mac

  • Replace the SSHPORT, SSHUSERNAME and REMOTEHOSTIP with the actual SSH/SFTP port, username and the host IP shown in your MyKinsta for this specific site ( You can find this information under the SFTP/SSH section of each site’s Info tab within MyKinsta.)

  • Replace SITEUSERNAME with the actual path of your site hosted on Kinsta server (that can be found under the “Environment details” path section in that site’s info tab within MyKinsta )

so that might look similar like this for example:

 docker run --rm -i \
  -v "/home/myuser/DevKinsta/public/amberscript":/target \
  -v "devkinsta_ssh":/tmp/.ssh \
  kinsta/devkinsta_rsync-ssh:1.3.0 \
  rsync --delete --timeout=60 -rz -L -e "ssh -p 20777 -o 'StrictHostKeyChecking no'" --info=progress2 --no-i-r amberusername@34.105.70.220:/www/amberusername_707/public/. /target/

Also, you may need to setup your valid SSH Key to your MyKinsta -> User Settings -> My Account -> SSH keys > Add SSH key as shown here (and here ).

It will then start to connect to the remote host (Kinsta server) and will start processing the rsync process to get/download the files from the remote server to your local computer (this may take some time, and files will be stored in that /home/myuser/DevKinsta/public/amberscript site folder with the example above).

Once completed, you may want to check the files/folders ownership under that site’s folder in question (might be set to root:root ). If that’s the case, you may want to perform this command line on your terminal to set it with your proper user/group ownership, something like this:

sudo chown -R myuser:myuser /home/myuser/DevKinsta/public/amberscript

Please give it a try and see if this manual rsync command will work and help to download your site’s files/folders to your local site’s folder on your computer.

Cheers,
Agus

Hey @Agus , we have just tested the code you’ve sent.

This is the result in my terminal:

The first docker run command is not complete I guess?
If we try the second nothing happend.

Scherm­afbeelding 2023-01-30 om 14.56.32

Please let us know what we can do!