HTTPS or SSL setup

These instructions are for the Private eazyBI version 3.0.0 or later.

If you want to enable HTTPS or SSL for Private eazyBI then you need to setup front-end web server (like Apache or ngnix) which will handle the HTTPS/SSL connection and will use the reverse-proxy to pass the request to Private eazyBI process.

Apache

Please follow any tutorial that describes how to setup Apache with SSL and a reverse proxy, for example, the following tutorial for Ubuntu.

If you use the same Apache web server as a reverse proxy for several applications then please also install and enable Apache mod_rewrite module and then you can use the following Apache virtual site configuration to proxy just the requests that start with /eazybi to Private eazyBI on localhost port 8080:

<VirtualHost *:443>
   # ...
   RequestHeader set X_FORWARDED_PROTO 'https'
   RewriteEngine On
   RewriteRule ^/(eazybi.*)$ http://127.0.0.1:8080%{REQUEST_URI} [L,P,QSA]
</VirtualHost>

Please also always set X_FORWARDED_PROTO as shown in this example as Private eazyBI will use the X-Forwarded-Proto HTTP header to detect that the original request used https protocol.

nginx

Please follow any tutorial that described how to setup nginx with SSL and a reverse proxy, for example, the first part of this tutorial.

If you use the same nginx web server as a reverse proxy for several applications then specify to proxy just the requests that start with /eazybi to Private eazyBI on localhost port 8080:

location /eazybi/ {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_pass http://127.0.0.1:8080;
}

Please always set the X-Forwarded-Proto HTTP header as Private eazyBI will use it to detect that the original request used https protocol.