(Separate Server for Subdomain) Seemingly successful use of Trellis, but production server seemingly not handling requests appropriately

trellis
3

First of all, thank you for taking the time to respond! As for your questions:

We try not to do guess work here too and we can’t truly help you unless you tell us the precise error you’re seeing and where you’re seeing it (e.g. in browser or in a log file?).

So I get no errors upon server setup / deployment via vagrant. My nginx access and error logs for blog.example.com are also blank.

When trying to access the website via browser, I get the following:

Chrome

The blog.example.com page isn’t working
blog.example.com didn’t send any data.
ERR_EMPTY_RESPONSE

Firefox

The connection was reset

The connection to the server was reset while the page was loading.

  • The site could be temporarily unavailable or too busy. Try again in a few moments.
  • If you are unable to load any pages, check your computer’s network connection.
  • If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

Did you search the forum/Google for your specific error?

I have searched far and wide via these forums, Google, and other resources. :slight_smile:

And speaking of log files, did you check your log files for errors?

See above, but willing to check any logs I may not have thought of.

What did you change each time you rebuilt your droplet?

So as far as the droplet (I am assuming DreamCompute’s instances are comparable) is concerned, nothing. I am using the stock Ubuntu 16.04 image and nuking it completely every time I change anything just to be sure.

As for Trellis changes, I have:

  • Provisioned the server via IP / Hostname (as suggested here: err_empty_response - #2 by ben)
  • Turned on / off multisite settings in wordpress_sties.yml (production) and the wordpress application.conf (and other changes suggested here: https://roots.io/trellis/docs/multisite/)
  • Enabled / disabled cache-ing (And other attempts to make it as consistent as possible with the Dev site)

I have also modified the server_name / root settings in the nginx config file for this site. I added a wildcard to the server_name and set the root to use the specific “release” folder instead of the relative “current” folder.

And just to reiterate, I wipe and rebuild the droplet / vagrant dev servers between changes and restore the Trellis files via git.

Please let me know if I am not being specific enough!