Kinsta deploy issue - problem cloning repo

trellis
1

Hi there, i’m having an issue while deploying to Kinsta. Everything works fine until last week. Now deployment stucks at cloning repo files (from bitbucket). I’ve tried everything (checked ssh keys and forwarding) but i can’t get it to work anymore.

  • I’ve generated a new ssh key (id_ed25519) and added it to Bitbucket and Kinsta.

  • My ssh/config looks like:

Host *
   UseKeychain yes
   ForwardAgent yes
   AddKeysToAgent yes
   IdentityFile ~/.ssh/id_ed25519

authenticated via ssh key.
You can use git to connect to Bitbucket. Shell access is disabled

Here you can see the error message:

Bildschirmfoto 2023-05-22 um 22.12.33
Bildschirmfoto 2023-05-22 um 22.12.331904×1010 164 KB

Thank you for any hints

2

Hi, I’m not too familiar with deployments to Kinsta but I just had a similar issue related to accessing BitBucket private repo during deployment. Found this: ACTION REQUIRED: Update your Bitbucket Cloud SSH Host Keys - Bitbucket

So I changed trellis/group_vars/all/known_hosts.yml to this:

# Documentation: https://roots.io/trellis/docs/troubleshooting/#composer-install-host-key-verification-failed

# Host keys to add to known_hosts, e.g.,
#   - git host for Bedrock-based project (`repo` variable in `wordpress_sites`)
#   - git hosts in Bedrock project's composer.json
known_hosts:
  - name: github.com
    key: github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
  - name: github.com
    key: github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
  - name: bitbucket.org
    key: bitbucket.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDQeJzhupRu0u0cdegZIa8e86EG2qOCsIsD1Xw0xSeiPDlCr7kq97NLmMbpKTX6Esc30NuoqEEHCuc7yWtwp8dI76EEEB1VqY9QJq6vk+aySyboD5QF61I/1WeTwu+deCbgKMGbUijeXhtfbxSxm6JwGrXrhBdofTsbKRUsrN1WoNgUa8uqN1Vx6WAJw1JHPhglEGGHea6QICwJOAr/6mrui/oB7pkaWKHj3z7d1IC4KWLtY47elvjbaTlkN04Kc/5LFEirorGYVbt15kAUlqGM65pk6ZBxtaO3+30LVlORZkxOh+LKL/BvbZ/iRNhItLqNyieoQj/uh/7Iv4uyH/cV/0b4WDSd3DptigWq84lJubb9t/DnZlrJazxyDCulTmKdOR7vs9gMTo+uoIrPSb8ScTtvw65+odKAlBj59dhnVp9zd7QUojOpXlL62Aw56U4oO+FALuevvMjiWeavKhJqlR7i5n9srYcrNV7ttmDw7kf/97P5zauIhxcjX+xHv4M=
  - name: bitbucket.org
    key: bitbucket.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIIazEu89wgQZ4bqs3d63QSMzYVa0MuJ2e2gKTKqu+UUO
  - name: gitlab.com
    key: gitlab.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAfuCHKVTjquxvt6CM6tdG4SLp1Btn/nOeHHE5UOzRdf
  - name: gitlab.com
    key: gitlab.com ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCsj2bNKTBSpIYDEGk9KxsGh3mySTRgMtXL583qmBpzeQ+jqCMRgBqB98u3z++J1sKlXHWfM9dyhSevkMwSbhoR8XIq/U0tCNyokEi/ueaBMCvbcTHhO7FcwzY92WK4Yt0aGROY5qX2UKSeOvuP4D6TPqKF1onrSzH9bx9XUf2lEdWT/ia1NEKjunUqu1xOB/StKDHMoX4/OKyIzuS0q/T1zOATthvasJFoPrAjkohTyaDUz2LN5JoH839hViyEG82yB+MjcFV5MU3N1l1QL3cVUCh93xSaua1N85qivl+siMkPGbO5xR/En4iEY6K2XPASUEMaieWVNTRCtJ4S8H+9

# Whether to automatically accept the host key for your `repo` (in `wordpress_sites`) during git clone.
# To avoid man-in-the-middle attacks, set this to `false` and add repo host key to `known_hosts` above.
repo_accept_hostkey: true
1 Like
3

@RistoKaalma Thx for your advice, but it still stucks at the same task [deploy : Clone project files]

4

After updating the above file as @RistoKaalma recommends, you’ll need to reprovision your server before attempting another deploy. Have you done that?

1 Like
5

@MWDelaney Yes i did but same behavior.

6

I don’t know why, but it’s working again since today :slight_smile: Maybe @RistoKaalma suggestion worked.

7

@MWDelaney adding new values to the remote server’s known_hosts file is actually a deployment (deploy.yml playbook) step.

But generally yes, when making changes in trellis/group_vars/all/known_hosts.yml, pushing these changes to project repo and then deploying then it should have worked assuming this was the case.

I’m glad to hear you got it working @wolfi!

1 Like