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.domain.com
- Obico Self-Hosted server IP: 192.168.2.10
- NGINX Proxy Manager IP address: 192.168.2.100
- 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 : obico.domain.com
- The
.envfile has the following environment variable set to:
SITE_USES_HTTPS=True
# set it to True if https is set up
SITE_IS_PUBLIC=True
# set it to True if the site configured in django admin is accessible from the internet
Setting up the DNS server
DNS server for domain.com 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 domain.com.
https://developers.cloudflare.com/fundamentals/api/get-started/create-token/
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 192.168.2.100