I'm trying to run my blog using ghost under nginx with ssl. I've successfully made it work with http using the following steps:
I'm getting a 502 - Bad Gateway while trying to access:
And every time I try to access the url above my nginx logs the following error:
I've been trying to solve this for hours to no avail. help please. asked 10 Dec '15, 02:48 jmiranda |
You won't be able to configure HTTPS on a private Nginx instance, nor should you ever need to do so unless accessing it directly on an open port in the firewall (which you are not doing and in general you would not do). The reason is that you're proxying the request through the server's front-end Nginx server; see this image (http://docs.webfaction.com/user-guide/_images/inside-the-server.png). The front-end Nginx server strips HTTPS and forwards HTTP to your application. The client (browser) negotiates the SSL handshake with the front-end Nginx server in that case, and we can install SSL certificates for you without you needing to manage them via a private Nginx. More information is available here (http://docs.webfaction.com/user-guide/websites.html#secure-sites-https). answered 10 Dec '15, 03:07 ryans ♦♦ Hi Ryans, I'm not well versed in networking software, but trying to understand what you said, the following statements are true?.
(10 Dec '15, 03:24)
jmiranda
(1) Yes, that's true in general, except when you need it for the actual application deployment. An example of that would be an Nginx+Passenger+Rails application. (2) Correct as of right now. Since requests go through the front-end Nginx server (which supports HTTP/1.1), this doesn't work yet. However we are currently considering the demand and implementation for this now that HTTP/2 is standardized.
(10 Dec '15, 06:27)
ryans ♦♦
Gotcha, thank you Ryans! :)
(10 Dec '15, 15:31)
jmiranda
|