Home Assistant Community Add-on: Nginx Proxy Manager

Hi,

I’m trying to run this add on. I have installed the mariadb ad on and started that, with a strong unique password but otherwise unchanged.

I now click start on this add on, but it simply doesn’t start (start button turns red).

I all ready have https (certificate generated by my qnap server) and duckdns (home assistant add on) set up and running fine, I just want to use this to forward a few subfolders to a few additional services I already have set up (but which are not currently externally accessible).

Any ideas why it wouldn’t start up?

1 Like

PS - even with trace level logs, nothing is output in the add-on logs.

PPS - I am running latest version of Hassio on a raspberry pi 4, with latest (non Beta) version of home assistant and supervisor.

1 Like

How to use this add on if i don’t wanna forward port 443 from my router to my raspberry? I would like to open for example port 11234 to my raspberry. What do i have to do to get the add on working with this port?

Trying to add a new subdomain but I receive this error, anyone knows why?

4/15/2020] [2:59:50 PM] [Express ] › :warning: warning Command failed: /usr/bin/certbot certonly --non-interactive --config “/etc/letsencrypt.ini” --cert-name “npm-8” --agree-tos --email “[email protected]” --preferred-challenges “dns,http” --webroot --domains “xxxx.duckdns.org
Saving debug log to /data/logs/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for xxxx.duckdns.org
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.
Waiting for verification…
Challenge failed for domain xxxx.duckdns.org
http-01 challenge for xxxx.duckdns.org
Cleaning up challenges
Some challenges have failed.

Is it possible to have HA as a sub folder?
Like subdomain.mydomain.com/ha while having another site on subdomain.mydomain.com configured on NPM.
I tried adding a custom path and using rewrite /ha/(.*) /$1 break; as suggested in various posts but i have a malformatted page as result ( a blank page with HACS text ).
Is there a solution for this?
Thanks

Might work but not supported (go through the above posts): https://github.com/home-assistant/architecture/issues/156#issuecomment-474528786

Ah!
Didn’t know that, I was thinking it could it be something wrong with the addon or some weird config to use.
Thanks for the info :raising_hand_man:

Hi, all! I’am trying enable nginx proxy manager addon without any domain names, using IPs only. Why it more difficult then with names. I have wireguard addon with own subnet? And I want any reqwest from its subnet redirects to another IPs. Can anybody little help me? M?)

Ola preciso de ajuda,
Estou instalando o Nginx e criando os hosts. Fiz a criação do HTTP e foi sucesso, porem quando edito para criar o SSL, ao salvar ele gera um Internal Error e no log do Nginx vejo a mensagem abaixo.
As portas ja estao liberadas no houter.

[5/5/2020] [7:03:13 PM] [Nginx ] › :information_source: info Reloading Nginx
[5/5/2020] [7:03:13 PM] [SSL ] › :information_source: info Requesting Let’sEncrypt certificates for Cert #5: xxxx.duckdns.org
[5/5/2020] [7:03:32 PM] [Nginx ] › :information_source: info Reloading Nginx
[5/5/2020] [7:03:32 PM] [Express ] › :warning: warning Command failed: /usr/bin/certbot certonly --non-interactive --config “/etc/letsencrypt.ini” --cert-name “npm-5” --agree-tos --email “[email protected]” --preferred-challenges “dns,http” --webroot --domains “xxxx.duckdns.org
Saving debug log to /data/logs/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for xxxx.duckdns.org
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.
Waiting for verification…
Challenge failed for domain xxxxx.duckdns.org
http-01 challenge for xxxx.duckdns.org
Cleaning up challenges
Some challenges have failed.

Has anyone used this addon to also make use of NGINX’s load balancer functions? I think it might be possible if I edit some of the config files manually…?

Is it possible to add the homeassistant directory to the image on boot?
I would like to write the logs of one instance to one of this directory to track my weather station :smiley:

br
manzn

Hi, and thank you for this add-on, among many others!

In regards to the mandatory prerequisite for mariadb, can somebody clarify if the add-on supports connection to an external mariadb instance? And how to configure it?

Many Thanks,
-a

can I only use port 443 for this? I don’t want to open port 443 to the outside world

I think you meant “I don’t want to open port 80 to the outside world”.

Port 443 is needed for accessing the services from outside the network. Port 80 needs to be accessible for renewing the certificate (thus is not required to be forwarded all the time).

Here’s an idea if you have a router capable of fiddling with firewall rules through command line (ie. DD-WRT, Tomato, OpenWrt, Asus Merlin):

  • set a sensor to measure remaining time until certificate is up for renewal;
  • create an automation running a script that adds port 80 to the FORWARDING chain on the router;
  • have the above automation set to trigger when the certificate is up for renewal;
  • automate monitoring of the certificate renewal;
  • create another automation to delete the rule for the port 80 forwarding after the certificate has been successfully renewed.

However, things complicate when you have multiple certificates to be renewed at different moments in time as you need to follow multiple sensors (and set the automations to rerun case the renewal process failed). In the end, it might be easier to just leave port 80 forwarded all the time.

1 Like

So far as I know there s no requirement to use port 443 in nginx and also I believe nginx will use a dns challenge for certificates instead of http on port 80. I don’t use nginx myself I use caddy and it certainly facilitates both those features.

Hi @oriolism @frenck , is there a solution to this issue?

I transitioned from core addon of ngnix proxy, to the community addon for ngnix proxy manager.
Now ipban captures and bans the docker ip of this addon, instead of real ip.

Not sure what else should be changed on the HA side and I’m confused on some aspects, for example:

  • Let’s encrypt container still required on the Home assistant side?
    Actually, i’m almost sure it’s not required, since port 80 should be now used only by the ngnix proxy manager container - but if i remove this container, how to regenerate the /ssl files on HA, without let’s encrypt?

  • base_url - should I continue to set it to the xyz.duckdns.org?

thanks,
-a

thank you. I managed it-
I just need to forward the port that I want in my router to 443 on my raspberry and everything works fine

I had the same problem , the resolution was enabling websockets support in NPM.

addon-nginx-proxy-manager/images/screenshot.gif at b3e7ab67f237d75fa26e60b1de1c6e1efe321e70 · hassio-addons/addon-nginx-proxy-manager · GitHub

Thanks @antimage, but I already have webockets enabled.

To answer your second question,
I have the base url set like this.

http:
  base_url: https://sub1.mydomain.duckdns.org

I dont have an ssl folder anymore, so i don’t think you would require it.
hope it helps.