# Fatal: [192.168.50.5] => SSH Error: Permission denied (publickey)

**URL:** https://discourse.roots.io/t/fatal-192-168-50-5-ssh-error-permission-denied-publickey/4566
**Category:** trellis
**Created:** 2015-08-25T05:00:01Z
**Posts:** 24
**Showing post:** 17 of 24

## Post 17 by @fullyint — 2015-08-27T05:28:07Z

Off the top of my head, I’m not sure what would cause that. Have you made sure your [site keys](https://github.com/roots/trellis/blob/8a84639257bdeaceb3b440823e2ac78c5c17906a/group_vars/staging#L4) are different for staging and production?

> [@Staging and Production on same VPS](https://discourse.roots.io/t/staging-and-production-on-same-vps/2440/23):
>
> It sounds like you’re running the `server.yml` playbook separately, once for `group_vars/staging`, then again for `group_vars/production`. You could possibly make that work if you change the “[site key](https://github.com/roots/trellis/blob/8a84639257bdeaceb3b440823e2ac78c5c17906a/group_vars/staging#L4)” in your `group_vars/staging` to something different, like `staging.example.com`. That way, when trellis creates [nginx conf files using that site key](https://github.com/roots/trellis/blob/8a84639/roles/wordpress-setup/tasks/nginx.yml#L39) name, you’ll in fact have two separate conf files.

You _will_ see the install WP install screen after your very first deploy, but you shouldn’t see the `wp-admin/setup-config.php` asking for database info etc.

---

_[View the full topic](https://discourse.roots.io/t/fatal-192-168-50-5-ssh-error-permission-denied-publickey/4566)._