i have my servers behind an AWS NLB. Because of the number of domains on the server, I can not put my certs on the NLB. Instead I have to enable Proxy Protocol v2 on the NLB/Target group.
Once I run this command (sudo site domain.com -ssl=on) I have to update the ssl config like so:
sudo sed -i 's/http2/http2 proxy_protocol/g' /etc/nginx/sites-enabled/domain.com
Unfortunately, once I do that the site turns "red" under site list
sudo site -list
https://d.pr/i/83h4hN
This apparently means that the site is no longer managed. When I updated to 1.9 and this file, wpcommon-noauth.conf, was added all of my "unmanaged" sites had http auth added because the "wpcommon-noauth.conf" was not updated on those sites.
My suggestion/request is to either default to add "proxy_protocol" when ssl is enabled. Both can be there and it won't affect anything. Or add a command line option to add it (sudo site domain.com -ssl=on -proxy_protocol=on)
Thanks for a great tool for site management and server setup. I've migrated half of my sites from EasyEngine to Webinoly on AWS with RDS and this is the only issue I've run into.