Home Assistant Community Add-on: Nginx Proxy Manager

No. I reinstalled the add-on and reconfigured the hosts.

Hi

This is the first time I’m working with this add-on since I just purchased a custom domain name. My goal is to forward plex.mydomain.com to my Plex server, ha.mydomain.com to my Home Assistant installation, etc.

The proxy hosts look like this:

The one for Plex works great. The one for HA however results in ā€œ400: Bad Requestā€. However, when I navigate to ha.mydomain.com:8123 it does work. But obviously I don’t want to enter the port number in the url.

My Home Assistant in itself is also able to resolve on a custom.duckdns.org:8123 domain but putting that as the destination gives the same error message.

Any ideas what I might be doing wrong here?

Edit: Nevermind. Bad case of RTFM: HTTP - Home Assistant

Is a wildcard duckdns domain + let’s encrypt cert + dns challenge possible with this addon?

I am using nginx manually configured on my openwrt + acme + duckdns and there it’s working.

I want to expose 4 services and this is currently my setup:

Is this setup possible also with an wildcard cert and dns challenge or do i have to get 4 duckdns domains?

thx

did you found a solution to redirect the access log somewhere ?
I would like to use a GoAccess for nginx proxy manager addon/docker to view a website portal with statistics.
using this: GitHub - xavier-hernandez/goaccess-for-nginxproxymanager: GoAccess Docker Image for Nginx Proxy Manager and more...

I did not found a HA addon for it, but I can make it with Portainer en paste a docker compose text there in the ā€œAdd Stackā€.

If I look at the Nginx Reverse Proxy Manager Addon with Portainer, I see following Volume mappings:

indeed the /mnt/data/supervisor/addon_configs/a0d7b954_nginxproxymanager is under my HA samba share undder addon_configs:

image

but the other share is not under addons directory (it is empty).

Anyone got GoAccess working with the HA NPM addon logs ?

edit: I think the logs are stored with HA under /var/log/journal ? (binary files)

with :
ha host logs --identifier addon_a0d7b954_nginxproxymanager
under supervsor ssh you can also see the log of the NPM.
Question now how to add this to the GoAccess docker compose file Volumes?

below something I tought it would be, but log is not available as file I think.

version: ā€˜3.3’
services:
goaccess:
image: ā€˜xavierh/goaccess-for-nginxproxymanager:latest’
container_name: goaccess
restart: always
ports:
- ā€˜7880:7880’
environment:
- TZ=Europe/Brussels
- SKIP_ARCHIVED_LOGS=False #optional
- DEBUG=False #optional
- BASIC_AUTH=False #optional
- BASIC_AUTH_USERNAME=user #optional
- BASIC_AUTH_PASSWORD=pass #optional
- EXCLUDE_IPS=127.0.0.1 #optional - comma delimited
- LOG_TYPE=NPM #optional - more information below
- ENABLE_BROWSERS_LIST=True #optional - more information below
- CUSTOM_BROWSERS=Kuma:Uptime,TestBrowser:Crawler #optional - comma delimited, more information below
- HTML_REFRESH=5 #optional - Refresh the HTML report every X seconds. GoAccess - Manual Page
- KEEP_LAST=30 #optional - Keep the last specified number of days in storage. GoAccess - Manual Page
- PROCESSING_THREADS=1 #optional - This parameter sets the number of concurrent processing threads in the program’s execution, affecting log data analysis, typically adjusted based on CPU cores. Default is 1. GoAccess - Manual Page
volumes:
- /mnt/data/supervisor/addons/data/a0d7b954_nginxproxymanager/logs:/opt/log
- /path/to/host/custom:/opt/custom #optional, required if using log_type = CUSTOM
networks:
- nginxproxymanager_default

networks:
nginxproxymanager_default:
external: true

Hello everyone,
I’ve used until yesterday, the two addon ā€œDuckDNSā€ and ā€œNGINX Home Assistant SSL proxyā€ and I could easily reach my HAS from the outside as https.

Now I would like to use https with the local address, i.e.:

https://192.168.1.100:8123
https://homeassistant.local:8123

I installed the ā€˜Nginx Proxy Manager’ addon:

But it doesn’t take the SSL certificate:

I ask your help on the following points:

  1. of course, I disabled the addon ā€˜NGINX Home Assistant SSL proxy’, but the question is:
    the addon ā€˜DuckDNS’ must be active with ā€˜Nginx Proxy Manager’?
    If yes, I set the following configuration and I would like to know if it is correct:
accept_terms: false
algo: secp384r1
certfile: fullchain.pem
keyfile: privkey.pem
  1. Is the following configuration that I set on the router correct?

  1. How should I configure the ā€˜Nginx Proxy Manager’ addon to use https also with local addresses?

Thanks in advance to anyone who will give me support.

I am currently having issues renewing my existing certificate… it seems duckdns is not resolving the name properly/issue with name record for some people… after spending hours messing with NPM and let’s encrypt this morning I finally found this post on Facebook which seems to allude to a DuckDNS issue at the moment… Redirecting...
So anyone with any further insight could please share if they are aware of a similar issue …

But this could possibly be your current issue.
I have two domains and the one from another dns provider checks out fine with https://letsdebug.net/

Thank you very much for your valuable contribution.

I noticed that I receive this warning:

warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-22" --agree-tos --authenticator webroot

I am now deactivating ā€˜Nginx Proxy Manager’’ and will return to using the official NGINX addon, at least for the moment. Hoping that the problems with DuckDNS will be resolved in a short time.

However, perhaps you could give me suggestions on the other points, in particular on how to use https also on local addresses?

Thanks again

I’m confused. Does this addon require MariaDB as a prerequisite?

The original post says yes:

  1. Ensure you are running the MariaDB add-on. This add-on is required to use the Nginx Proxy Manager add-on as it uses the database services provided.

However, the official documentation makes no mention of MariaDB. Ditto for the addon instructions.

If MariaDB is indeed a dependency, what precisely does that mean? Does my HA installation need to already have been migrated to MariaDB (from the default SQLite), or does this addon simply need to create its own database using MariaDB?

It was the breaking change of that release that states Mariadb is no longer required.

I am a confused noob, I used NGINX Home Assistant SSL proxy addon with no problems, I thought to change it with nginx proxy manager to manage proxies and solve some problems due to iframes (not ssl pages) but I had some configurations problem.

what I do:
-deactivate NGINX Home Assistant SSL proxy it is right? or I have to keep it?

I think reply is YES, but I have problem on make nginx proxy manager work properly, my open port on router is 8126 and it is the port on ha ssl I have a subdomain on duckdns and certificate was issued with ok.

so I configured this:

NGinx Proxy Manager Admin web interface: 8081
HTTPS/SSL Entrance port: 8126

and proxy host:
xxxx.duckdns.org:8126

https
Forward Hostname / IP* 192.168.0.50
Forward Port 8126

force ssl
http/2 support on

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection ā€œupgradeā€;

it is correct? because something is wrong… I have no access

I sorted out to make it working with the ha 8126, but now I have to use nginx proxy manager to create an ssl port for my device (wled) 192.168.0.158 how to do it?

You are a legend!

I am currently changing my reverse proxy to NGINX myself and ran into issues until I found your post.

Should be stickeyed.

Thank you!

Necro Post lol!

This worked perfectly for me, just wanted to pop by and say thank you! :slight_smile:

It’s been awhile since you posted this, but I’m trying to do the same thing. Running HassOS and having a hell of a time trying to find where everything is saved.
I don’t see anything in /var/log/journal…

Hoping you came up with something to make this work for you!

Thank you!

Hi @frenck

When upgrading from 1.0.1 to 2.0.0 I’m seeing CPU spikes in docker stats and the overall CPU usage is impacted due to this upgrade.

Is there any place I can log this as an issue

See thread 2025.7: That's the question - #263 by _dev_null