NGINX Proxy Configuration

  • Home
  • Docs
  • NGINX Proxy Configuration

Configuring an NGINX Proxy for self-hosted Userify

For self-hosted Userify installations (Express and Enterprise), we recommend you install NGINX for much faster dashboard operation:

curl | sudo -sE

That script is preferred for a default-installed Userify installation on Ubuntu Linux.

You can also build a similar configuration by hand; here is a sample NGINX Configuration to the following to terminate TLS at the NGINX server and send all requests for paths beginning with /api directly to the Userify server(s) started in the multi-core scripts.

upstream proxybackend {
    server       weight=5;

server {

      # recommended (adjust as needed)
      proxy_buffers 256 8k;

      # add other NGINX configuration as needed.

      root /opt/userify-server/web/;
      index index.html;

      location / {
            try_files $uri $uri/ 404;
      location /api {
            proxy_redirect off;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            # optional for multi-core use above:
            proxy_pass http://proxybackend;
      location / {
            root /opt/userify-server/web/shim/ ;
      location / {
            root /opt/userify-server/web/shim/ ;

See for more details. The above server section is intended to be within a larger http section. For example:

user nobody;
worker_processes 16;
pid /var/run/;
error_log /var/log/nginx/error.log info;

events {
    worker_connections 768;
    multi_accept on;

http {
    # .... see above

See also Autoscaling and Secure VPC architecture. (Note: HA Proxy may be a better option for this use case.)

Get More Information

Please fill out the form below to receive more information. If you are inquiring about purchasing Userify, please be sure to include your company name, number of servers and users, and the Userify edition that you are interested in.