Providing SSH access for migration to Kinsta

Hi guys,

I’m currently migrating an existing site to Kinsta. Setting up a new site has been great, for the assisted migration however I’m asked to provide access to my current DigitalOcean server via SFTP or SSH.

I’m unsure how to provide external access to my Trellis installation to give access for Kinsta Support. Does anyone have any experience with this?


Have you seen

You can either add a new user + ssh key or add the key to an existing user (such as the admin user).

Thanks for your reply @swalkinshaw.

I am hoping to provide Kinsta access with a password instead of adding a key. Will I be able to share the ‘{{ admin_user }}’ password in the production .vault file, and have them be able to SSH into the droplet via ‘ssh’? Or is this the wrong approach?

In trellis/group-vars/all/security.yml you’ll see

# Documentation:
# If sshd_permit_root_login: false, admin_user must be in 'users' (`group_vars/all/users.yml`) with sudo group
# and in 'vault_users' (`group_vars/staging/vault.yml`, `group_vars/production/vault.yml`)
sshd_permit_root_login: false
sshd_password_authentication: false

I would imagine that if you change the second one to true, you’ll be able to hand over a password.


@ng3 Awesome, thanks for the quick reply. I will change this setting, re-provision and handover the details. Hopefully this will be enough for Kinsta to migrate.

1 Like

No worries! I hope it worked…

This topic was automatically closed after 42 days. New replies are no longer allowed.