# Issues with provison using ansible on Kinsta/Trellis/Bedrock site

**URL:** https://discourse.roots.io/t/issues-with-provison-using-ansible-on-kinsta-trellis-bedrock-site/18748
**Category:** trellis
**Tags:** ansible, kinsta, trellis
**Created:** 2020-07-23T17:46:22Z
**Posts:** 4

## Post 1 by @pmceldowney — 2020-07-23T17:46:22Z

I’m having a bit of trouble getting my Trellis site to provision my kinsta server. I’ve created public ssh keys on my Mac and added the path in /all/users.yml. Let’s use my staging environment as an example.

In /staging/vault.yml do I need match the user\_password with the ssh/sftp password on my kinsta dashboard? The guide i followed ([Deploying Trellis-based WordPress Sites to Kinsta | Roots](https://roots.io/guides/deploying-to-kinsta-with-trellis/)) only mentioned adding db\_password, db\_name, db\_user but nothing about the user\_password. There was also no mention of the admin\_user in /all/users.yml. It comes default as “admin” but do I need to change that to the user name for ssh/sftp in my Kinsta dashboard?

I tried to run `ansible-playbook server.yml -e env=staging` with **admin** as the username and that return with a “permission denied” error, which makes sense since it tried to connect to the kinsta server as admin@xx.xx.xx.xxx. So I changed the **admin\_user** to what is in my kinsta dashboard and ran `ansible-playbook server.yml -e env=staging` again and it returned with this error

 ![Screen Shot 2020-07-23 at 12.35.25 PM](https://discourse.roots.io/uploads/default/original/2X/e/ea66c1842fd4e349d0707015c2c112613f668c3f.png)

I’m also able to ssh into my kinsta server with no issue using `ssh example@xx.xx.xx.xxx -p XXXXX`

Has anyone had similar issues?

---

## Post 2 by @alwaysblank — 2020-07-23T17:48:08Z

> [@pmceldowney](#):
>
> I’m having a bit of trouble getting my Trellis site to provision my kinsta server.

Trellis cannot provision Kinsta servers, it can only deploy to them. This is stated in the article you linked:

> Trellis can deploy to Kinsta with just a few updates. Since Kinsta provides everything from the web server standpoint, provisioning your staging and production environments do not apply.

---

## Post 3 by @pmceldowney — 2020-07-23T17:55:08Z

That clearly went right over my head…thanks! Would you mind explaining a bit about the users between Kinsta and Trellis though? I’m still having a hard time wrapping my head around it. Does admin\_user need to match the user name in Kinsta or does just the web\_user in /staging/main.yml need to match the kinsta user name for that environment?

---

## Post 4 by @alwaysblank — 2020-07-23T18:10:30Z

Because Trellis isn’t provisioning, I don’t believe it needs the `admin_user`–it won’t be doing any tasks that require administrative permissions. I don’t believe Kinsta will even allow you to take administrative actions when logged in via SSH.

The `web_user` is required because that’s how Trellis will log in via SSH. It’s the user name Kinsta gives you for that environment. (Unless you change them, the only thing that actually varies between Kinsta environments is generally the SSH/SFTP port.)

---

## Post 5 by @system — 2020-09-03T17:46:26Z

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