# Deploy Clone Project Files dictionary error

**URL:** https://discourse.roots.io/t/deploy-clone-project-files-dictionary-error/5607
**Category:** trellis
**Created:** 2016-01-02T19:21:09Z
**Posts:** 12
**Showing post:** 4 of 12

## Post 4 by @fullyint — 2016-01-02T21:09:10Z

> [@jwkicklighter](#):
>
> `msg: [Errno 2] No such file or directory`

I can’t remember off the top of my head, but this might be one of two things:

**1.** Check on your usage/non-usage/value of [`repo_subtree_path`](https://github.com/roots/trellis/blob/e849bf9ea8901034115d8886692a55288728c186/group_vars/production/wordpress_sites.yml#L9). I’m not sure which version of Trellis you are using, so note that the `subtree` variable was renamed `subtree_path` on [Sep 6, 2015](https://github.com/roots/trellis/pull/329), then `repo_subtree_path` on [Dec 29, 2015](https://github.com/roots/trellis/pull/451). You could find more info by searching `subtree` in discourse and docs.

**2.** Double-check that you have committed your updated composer files to the [repo](https://github.com/roots/trellis/blob/97a9c05e3479af370a551682d9a689e6763b5d2f/group_vars/staging/wordpress_sites.yml#L7) that is cloned during deploy, like [Downgrade WP when deploy - #6 by swalkinshaw](https://discourse.roots.io/t/downgrade-wp-when-deploy/5574/6).

> [@jwkicklighter](#):
>
> it appears that I cannot ssh into the droplet without using the root user.

Try changing `web_user: web`, running `server.yml`, then testing `ssh web@45.55.227.142`. When you run `server.yml` its [`users` role](https://github.com/roots/trellis/blob/e849bf9ea8901034115d8886692a55288728c186/server.yml#L21) adds [these users](https://github.com/roots/trellis/blob/e849bf9ea8901034115d8886692a55288728c186/group_vars/all/users.yml#L5-L17) to the server, so you and ansible can then ssh as `admin` and `web`. If that doesn’t work, then there is more debugging to do, and I’d start with this (even though it shouldn’t be directly related to issue of whether `web` can make an ssh connection):

> [@fullyint](#):
>
> If you run into trouble after changing `web_user` back, there’s some chance that you’ll need to destroy/rebuild the droplet and rerun with `web_user: web`. I haven’t tested, but I suspect it’s possible that running everything once with `web_user: root` could cause permissions/ownership issues that might not resolve with just rerunning with `web_user: web`.

---

_[View the full topic](https://discourse.roots.io/t/deploy-clone-project-files-dictionary-error/5607)._