# Successfully provisioned and deployed my server(all green), no wordpress page though

**URL:** https://discourse.roots.io/t/successfully-provisioned-and-deployed-my-server-all-green-no-wordpress-page-though/10905
**Category:** trellis
**Tags:** trellis
**Created:** 2017-11-15T05:18:47Z
**Posts:** 11
**Showing post:** 11 of 11

## Post 11 by @fullyint — 2017-11-30T02:15:10Z

Here’s what sticks out to me:

> [@digitalnomad](#):
>
> I have not updated my hosts file. I just go directly to the ip in my browser.

It makes me think of the following, which is just another way of saying what others have been saying:

> [@err_empty_response](https://discourse.roots.io/t/err-empty-response/6225/3):
>
> If you’re saying you’ve run `server.yml` and `deploy.yml` then you point your web browser at your IP and get an empty response, I speculate that it is because your Nginx isn’t configured to process requests to the IP name, only the domain name. Here are the [`site_hosts`](https://github.com/roots/trellis/blob/e0fee339fd72123b7e7accab4a2367de895995a1/group_vars/production/wordpress_sites.yml#L7-L10) for which your server will process requests. By default, this doesn’t include the IP.
> 
> Ultimately, you’ll want to connect using a fqdn once you have DNS set up. If that is not yet set up, I’d recommend making an entry in your local machine’s `/etc/hosts`  
> `146.185.132.84 mydomain.com`  
> then point your browser at `mydomain.com` instead of the IP.

If perhaps this is a multisite installation, note this section in the [multisite docs](https://roots.io/trellis/docs/multisite/):

> After provisioning your remote server and deploying your sites, you’ll need to install WordPress as a final step in your staging and production environments. SSH into your server as the `web` user …

---

_[View the full topic](https://discourse.roots.io/t/successfully-provisioned-and-deployed-my-server-all-green-no-wordpress-page-though/10905)._