Hi guys, It’s my first time deploying Trellis to DigitalOcean. Everything seems to be going fine, except i’m receiving the following message going to my droplet’s IP: 146.185.132.84 didn’t send any data. ERR_EMPTY_RESPONSE Reading up it seemed perhaps it had to do with SSH agent forwarding (which…

I agree with @ben Given that I had most of this typed, I’ll still send it along… 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…

Thanks guys, for the quick help. I get what the problem is now: using the IP. [image] ben: Did you provision the server with an actual hostname? I did not, i’m using the droplet’s IP, which, I believe now, is causing the issue. [image] fullyint: Ultimately, you’ll want to connect using …

If you’re showing the client the site on your machine, you could use the approach I mentioned of adding a temporary entry to your /etc/hosts. But more likely, you want enable the client to visit the site on their own devices and you don’t expect them to mess with /etc/hosts. There could be many app…

Thanks guys the issue has been resolved! [image] fullyint: I’d set up DNS to point staging.mydomain.com to a different IP This is indeed what I did. Staging is now done in a subdomain, with it’s own droplet. For future reference: The error: ERR_EMPTY_RESPONSE The cause: Trying to work wit…

err_empty_response

trellis

ben March 16, 2016, 6:39pm 2

Did you provision the server with an actual hostname? You’ll need to use that instead of an IP address.

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