# Getting started with Trellis for multiple domains

**URL:** https://discourse.roots.io/t/getting-started-with-trellis-for-multiple-domains/9365
**Category:** trellis
**Created:** 2017-04-12T04:54:36Z
**Posts:** 9
**Showing post:** 7 of 9

## Post 7 by @fullyint — 2017-04-18T21:16:12Z

`ERR_EMPTY_RESPONSE` makes it sound like there isn’t a functional nginx conf for site.dev. The nginx conf would be created/updated in the [wordpress-setup role](https://github.com/roots/trellis/blob/1f165ead7b22d8dd1dd88294ae4d7c71849b5a74/dev.yml#L22), so we really only need to run the `wordpress` tags of the playbook. Try this:

```
SKIP_GALAXY=true ANSIBLE_TAGS=wordpress vagrant reload --provision
```

then run

```
vagrant hostmanager
```

then try loading site.dev in a new browser tab. If it still doesn’t work, you could `vagrant ssh` and inspect the nginx confs in `/etc/nginx/sites-enabled` to ensure they look correct to you.

Notes on the commands:

- `SKIP_GALAXY` saves some time because you already have those roles installed
- `ANSIBLE_TAGS` runs only the relevant roles
- `reload` is to ensure that vagrant has synced up the two bedrock `site` directories
- `--provision` is so that it runs the `dev.yml` playbook and its roles tagged `wordpress`
- [`vagrant hostmanager`](https://github.com/devopsgroup-io/vagrant-hostmanager#usage) updates the entries in `/etc/hosts` to ensure your browser will serve from the VM instead of real public DNS.

* * *

As for the security risks of multiple sites on the same server, I’m not a pro on the topic, but it seems safe to say that the nature of the risk depends on the nature of the compromise. In general, of course, any given site would be safer on its own separate server, unless that means the caretaker is overwhelmed and not being as vigilant. I’m not aware of Trellis attempting any special sandboxing between sites on the server, however.

---

_[View the full topic](https://discourse.roots.io/t/getting-started-with-trellis-for-multiple-domains/9365)._