Skip to main content

Obico Reverse Proxy with NGINX Proxy Manager


Security Warning: The guide below only cover the basic steps to set up a reverse proxy for self-hosted Obico Server. The setup required to properly secure your private network is too complicated to be covered here. Please do your own research to gather the necessary info before you proceed.


This is a community-contributed guide. This guide is based on certain Obico community members' own setup and hence may not work for you.


If this guide doesn't work for you, you can try your luck by following another community-contributed guide to set up NGINX reverse proxy.

Assumptions for this guide

  • FQDN of the Obico public server:
  • Obico Self-Hosted server IP:
  • NGINX Proxy Manager IP address:
  • Available public IP address which is either fixed if DHCP is used a DDNS mechanism is in place to update the DNS record of the firewall FQDN
  • Full access to the DNS server in setting up DNS records in order to get certificate issued automatically via NGINX Proxy Manager. In this example Cloudflare is used as the DNS server
  • Obico Self Hosted server Django site name has been set to :
  • The .env file has the following environment variable set to:

# set it to True if https is set up

# set it to True if the site configured in django admin is accessible from the internet

Setting up the DNS server

DNS server for requires the following record:

obico A [public IP address]

This next record is required to enable the tunnel within the Obico apps or web gui.

*.tunnels.obico A [public IP address] ( this can also be a CNAME record pointing to the obico A record)

In Cloudflare you will need to create an API token to allow updates since Let’s Encrypt in NGINX Proxy Manager will need to insert some TXT DNS record to verify you have control of

Select your domain and give it the Edit permission.

Make sure to write down the API Token as it will be needed in NGINX later and you can’t go back, and view again once created. You would have to delete and recreate a new one.

Configuring the firewall

Port Forwarding:

Port 80 and 443 requires to be forwarded to the NGINX Proxy Manager internal IP address

Setting up NGINX Proxy Manager on docker

I have used the following to setup NGINX Proxy Manager:,Nginx%20Proxy%20Manager%20has%20configured

The docker file docker-compose.yml contains the following:

version: '3.8'
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
- '80:80'
- '81:81'
- '443:443'
- ./data:/data
- ./letsencrypt:/etc/letsencrypt

Required SSL certificates for using NGINX Proxy Manager and the Obico self-hosted server

In order to have the Obico self-hosted server available from a public facing IP address and also having the tunnels being created to access the printer WebUI a minimum of 2 certificates will be required:

For the main website you will need to create a Let’s Encrypt certificate.You can either create a wildcard certificate * or or a certificate that covers both.

You will also need to create one more wildcard for * You have to create this one by itself as wildcard certificate can only use one subdomain therefore a * would not cover the tunnels.obico subdomain. Failing to do so will prevent the tunnels from being created.

In the NGINX Proxy Manager webgui under SSL Certificates click “Add SSL Certificates”

Make sure to use “DNS Challenge” inserting your previously created API token in the required field.

Firewall port forwarding must be enable for port 80 to the NGINX Proxy Manager host for the DNS Challenge to work.

Create both certificates using the following settings:

Once completed you should have under SSL certificates the following:

The hidden part should be

In the “Hosts” section you will need to create to port forwarding to the Obico self-hosted server at and port 3334 for *

In the SSL Option you will need to select the wildcard SSL certificate previously created for the * with these settings.

Click Save.

A second proxy host needs to be created for the main site with the same process this time selecting the other wildcard or dedicated SSL certificate.

Once these are created you should now be able to access your self-hosted Obico server from the url and activate the tunnel to your printer WebUI.