Home Assistant Community Add-on: Nginx Proxy Manager

[firebass08 (James)]

@RichardU what version was the issue? what version is the factory reset?
I’ve found my unifi is also blocking port 80, even though I have the port forward set.

[RichardU (Richard)]

Everything was the latest version when it happened - Dream Machine Pro. My suspicion is that it happened because I initially set up my Unifi while connected through another router. After the factory reset, I connected Unifi directly to my fiber connection and it worked.

[eseelke (Eddie Seelke)]

Did you ever find a solution for this?

[andriej]

If certificate is renewed (not generated) the npm value doesn’t change.
So I use that path in all my addons and it’s working.

[FreekBos]

A life saver… thanks!!!

[matteos1 (Matteo)]

after update there is an error when try to enter…

some solution?

[21:57:06] INFO: Starting the Manager…
[10/24/2020] [11:57:10 PM] [Global ] › error Cannot find module ‘…/global/certbot-dns-plugins’
Require stack:

• /opt/nginx-proxy-manager/internal/certificate.js
• /opt/nginx-proxy-manager/internal/proxy-host.js
• /opt/nginx-proxy-manager/internal/report.js
• /opt/nginx-proxy-manager/routes/api/reports.js
• /opt/nginx-proxy-manager/routes/api/main.js
• /opt/nginx-proxy-manager/app.js
• /opt/nginx-proxy-manager/index.js Error: Cannot find module ‘…/global/certbot-dns-plugins’
  Require stack:
• /opt/nginx-proxy-manager/internal/certificate.js
• /opt/nginx-proxy-manager/internal/proxy-host.js
• /opt/nginx-proxy-manager/internal/report.js
• /opt/nginx-proxy-manager/routes/api/reports.js
• /opt/nginx-proxy-manager/routes/api/main.js
• /opt/nginx-proxy-manager/app.js
• /opt/nginx-proxy-manager/index.js
  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:965:15)
  at Function.Module._load (internal/modules/cjs/loader.js:841:27)
  at Module.require (internal/modules/cjs/loader.js:1025:19)
  at require (internal/modules/cjs/helpers.js:72:18)
  at Object. (/opt/nginx-proxy-manager/internal/certificate.js:16:26)
  at Module._compile (internal/modules/cjs/loader.js:1137:30)
  at Object.Module._extensions…js (internal/modules/cjs/loader.js:1157:10)
  at Module.load (internal/modules/cjs/loader.js:985:32)
  at Function.Module._load (internal/modules/cjs/loader.js:878:14)
  at Module.require (internal/modules/cjs/loader.js:1025:19) {
  code: ‘MODULE_NOT_FOUND’,
  requireStack: [
  ‘/opt/nginx-proxy-manager/internal/certificate.js’,
  ‘/opt/nginx-proxy-manager/internal/proxy-host.js’,
  ‘/opt/nginx-proxy-manager/internal/report.js’,
  ‘/opt/nginx-proxy-manager/routes/api/reports.js’,
  ‘/opt/nginx-proxy-manager/routes/api/main.js’,
  ‘/opt/nginx-proxy-manager/app.js’,
  ‘/opt/nginx-proxy-manager/index.js’
  ]
  }
  [21:57:10] INFO: Starting the Manager…
  [10/24/2020] [11:57:13 PM] [Global ] › error Cannot find module ‘…/global/certbot-dns-plugins’
  Require stack:
• /opt/nginx-proxy-manager/internal/certificate.js
• /opt/nginx-proxy-manager/internal/proxy-host.js
• /opt/nginx-proxy-manager/internal/report.js
• /opt/nginx-proxy-manager/routes/api/reports.js
• /opt/nginx-proxy-manager/routes/api/main.js
• /opt/nginx-proxy-manager/app.js
• /opt/nginx-proxy-manager/index.js Error: Cannot find module ‘…/global/certbot-dns-plugins’
  Require stack:
• /opt/nginx-proxy-manager/internal/certificate.js
• /opt/nginx-proxy-manager/internal/proxy-host.js
• /opt/nginx-proxy-manager/internal/report.js
• /opt/nginx-proxy-manager/routes/api/reports.js
• /opt/nginx-proxy-manager/routes/api/main.js
• /opt/nginx-proxy-manager/app.js
• /opt/nginx-proxy-manager/index.js
  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:965:15)
  at Function.Module._load (internal/modules/cjs/loader.js:841:27)
  at Module.require (internal/modules/cjs/loader.js:1025:19)
  at require (internal/modules/cjs/helpers.js:72:18)
  at Object. (/opt/nginx-proxy-manager/internal/certificate.js:16:26)
  at Module._compile (internal/modules/cjs/loader.js:1137:30)
  at Object.Module._extensions…js (internal/modules/cjs/loader.js:1157:10)
  at Module.load (internal/modules/cjs/loader.js:985:32)
  at Function.Module._load (internal/modules/cjs/loader.js:878:14)
  at Module.require (internal/modules/cjs/loader.js:1025:19) {
  code: ‘MODULE_NOT_FOUND’,
  requireStack: [
  ‘/opt/nginx-proxy-manager/internal/certificate.js’,
  ‘/opt/nginx-proxy-manager/internal/proxy-host.js’,
  ‘/opt/nginx-proxy-manager/internal/report.js’,
  ‘/opt/nginx-proxy-manager/routes/api/reports.js’,
  ‘/opt/nginx-proxy-manager/routes/api/main.js’,
  ‘/opt/nginx-proxy-manager/app.js’,
  ‘/opt/nginx-proxy-manager/index.js’
  ]

[Taronaga]

Same problem after update.
until I stopped the extension, the processor load increased significantly

[Msv1]

I see the same error, and are also not able to login

[Moogles (Moogels)]

Same here. Can’t login to Nginx Proxy Manager. I get “Bad Gateway” when I try enter Email and password.

[snarby]

Same here, with same error in logs

[Petrica (PetricaM)]

Same, had to restore addon from snapshot and then disable auto update.

[tteck (𝙩𝙩𝙚𝙘𝙠𝙨𝙩𝙚𝙧)]

Update 0.8.1 fixed all problems for me.

[Ronaldt (Ronald ter Veen)]

No need to disable the auto update, it was fixed in 0.8.1:

Can't install v0.8.0 - Cannot find module '../global/certbot-dns-plugins'

[Ronaldt (Ronald ter Veen)]

Is there by any change an event that is triggered just before a certificate is going to be renewed? I’d like my port 80 closed until the HTTP-01 challenge, open the port and close it after it updated the certificate.

[Lucan]

Just want to say thank you - awesome plugin!

[heachhog]

Cross posting from the thread I started, perhaps this would get more visibility here ( link to the thread NGINX (Proxy Manager) + basic auth + websockets = experiencing issues )

Hey everyone,

I have been going crazy, trying to figure this one out but yet to find a solution. I am running Home Assistant Supervised 0.116.4 on Intel NUC. Now, I am trying to configure easy external access to the system with a custom domain.

I installed NGINX Proxy Manager addon and configured the domain I want to use and enabled websocket support. This part works ( I can access HA and all pages inside, Lets Encrypt installed SSL, etc.).

After adding basic HTTP auth (so I am not leaving the interfaces fully exposed), the connectivity issues start. Entering the basic auth credentials and then logging into HA instance is OK, but then, for some reason, I am getting 401 error (Authorization Required) when accessing other HA pages (e.g. logs). It seems that WebSockets URL are not being proxies properly or not passing the authentication header.

In NPM logs, I can see these lines:

Copy to clipboard

[19/Oct/2020:11:18:22 +0200] - - 401 - GET https ha.example.com "/config/logs" [Client 12.12.12.12] [Length 574] [Gzip -] [Sent-to 192.168.0.198] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36" "https://ha.example.com/config/dashboard"
[19/Oct/2020:11:18:24 +0200] - - 401 - GET https ha.example.com "/service_worker.js" [Client 12.12.12.12] [Length 574] [Gzip -] [Sent-to 192.168.0.198] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36" "https://ha.example.com.xyz/service_worker.js"

Considering that I haven’t really made any changes to the networking/HTTP configuration of Home Assistant, do I miss on any configurations in NPM/Nginx itself to support basic auth? Any help here is appreciated, just point me in the right direction

[boesing]

Recently, my NPM started to show 403 Forbidden. I’ve just updated to Home Assistant 0.117 (probably it started in an earlier version, can’t really say).

Any ideas?

[Petrica (PetricaM)]

@heachhog

After adding basic HTTP auth (so I am not leaving the interfaces fully exposed), the connectivity issues start.

Why would you need this for Home Assistant?

As an additional security measure for an exposed HA instance you should always enable MFA but I don’t see the point of enabling NPM auth on HA addon (and probably with the same password as with HA).

[Petrica (PetricaM)]

Sorry for not being able to help; however, how would you expect other persons to help you if you don’t give any details on your setup?

How to help us help you - or How to ask a good question

Before we begin… This forum is not a helpdesk The people here don’t work for Home Assistant, that’s an open source project. We are volunteering our free time to help others. Not all topics may get an answer, never mind one that helps you solve your problem. [image] This also isn’t a general home automation forum, this is a forum for Home Assistant and things related to it. Any question about Home Assistant, and about using things with Home Assistant, is welcome here. We can’t help you with e…

[heachhog]

The plann was (perhaps still is) to have some additional apps behind the reverse proxy, where they might not havea good auth mechanism(and/or 2FA). I’ve gone ahead and enabled 2FA and left HA with that for now. So it can be considered as resolved.

With that being said, the issue that HA doesn’t work with HTTP auth still remains and the question here - is it a bug or it is never meant to work with it in the first place?