How to get nginx mainline working with EasyEngine


#1

Been using EE for about a year now (maybe a little longer), and want to give HTTP/2 a shot. From what I’ve read, this requires --nginxmainline. For whatever reason, EE keeps complaining when I remove nginx and put mainline in its place. It doesn’t recognize the argument.

Here’s what I’m trying to do:

ee stack remove --nginx
ee stack install --nginxmainline

Here’s what EE said:

# ee stack install --nginxmainline
usage: ee stack (command) [options]
ee: error: unrecognized arguments: --nginxmainline

I’ve updated EE, and am on the latest release:

# ee -v
EasyEngine v3.7.2

…and here is the nginx info for what’s currently in place…

# ee info --nginx

NGINX (1.10.0):

user                             www-data
worker_processes                 auto
worker_connections               4096
keepalive_timeout                30
fastcgi_read_timeout             300
client_max_body_size             100m
allow                            127.0.0.1

Any ideas? Pulling my hair out. Maybe the docs are wrong/outdated?


#2

DOCS: HTTP/2 support


#3

Ugh, just noticed the message about mainline being removed. It was in the docs, but not sure why that page (with all the mainline commands) actually still exists, if it’s been removed…with a comment at the top saying “removed”. Seems a little counter-productive.

I was originally working from this link, if it helps anyone else searching:

https://easyengine.io/blog/new-release-http2-letsencrypt-support/


#4

@ashworthconsulting – From what I recall all I did was setup a site using the LetsEncrypt argument from a normal EE install.

Once the site is setup inside of my ssl.conf file for this domain I have:

listen 443 ssl http2;

Full output of ssl.conf is:

listen 443 ssl http2;
ssl on;
ssl_certificate     /etc/letsencrypt/live/brianjking.me/fullchain.pem;
ssl_certificate_key     /etc/letsencrypt/live/brianjking.me/privkey.pem;

After that I just ran a service nginx reload and tested the site at https://tools.keycdn.com/http2-test and via Chrome’s console and it’s definitely loading over HTTP/2.


HTTP/2 on website created with ee create example.com --wpfc?
EE has Nginx compiled with SPDY?
#5