# 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:** 19 of 24

## Post 19 by @buretta — 2015-09-01T05:49:23Z

I’ve redone the vanilla setup. Things worked, however my attempt to have both staging and production on the same droplet was were I got stuck. It was my assuming the ansible setup was intended for this but (as you mentioned) 2 separate droplets are preferred. 1 for staging and the 2nd for production.

Reading this thread things became more clear [Staging and Production on same VPS - #8 by btamm](https://discourse.roots.io/t/staging-and-production-on-same-vps/2440/8)

If I am going to have staging and production on the same server I can ignore the staging and use a subdomain that is defined in the production group\_\_vars.

> [@Staging and Production on same VPS](https://discourse.roots.io/t/staging-and-production-on-same-vps/2440/5):
>
> bedrock-ansible lets you define multiple WP sites on a server. Although I just realized it’s a little weird with the environment naming right now. For example, by default there’s group\_vars/staging and group\_vars/production. You’d probably want to just pick production and define 2 sites in there and vary the env.wp\_env setting. You’d also need to define the server ip under hosts/production.
> 
> You can run the playbook as normal in Ansible like ansible-playbook -i hosts/production site.yml

FInal assumption, if I go with the above I would then run

```
./deploy.sh production mysite.com
./deploy.sh production staging.mysite.com
```

Is there a way to target a specific branch on deploy?

---

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