> Create an initial default server for failover on the ip address, and have it
> 400 everything. Do it for http and https. For https you can use a
> self-signed cert; it doesn't matter as you only need to be a valid protocol.
> # failover http server
># failover https server
You don't
On Dec 4, 2016, at 11:03 AM, Reinis Rozitis wrote:
> In case of https I don't even think it makes sense to provide any
> certificates (even self-signed).
> Without those the connection will/should be just terminated because of peer
> not providing any certificates and self-signed certs shouldn
We've used nginx for years and never had an issue with nginx upgrade
until today where the upgrade command ran but almost instantly after the
new process exited.
/usr/local/etc/rc.d/nginx upgrade
Performing sanity check on nginx configuration:
nginx: the configuration file /usr/local/etc/nginx/
