This is a really nice add-on, and I got it all working, but I’m wondering a bit about best practices.
In which cases should I NOT enable Websockets support and/or HTTP/2 Support? I have them all enabled atm.
Should I be using the same certificate for all instances on the same server, or should I have separate for each? At the moment, I’m using the same for HA and Node-Red, but a separate one for a website I’m hosting.
I tried so hard to make this work but can’t.
Everything goes well until I request SSL and I get internal error
Of note I have the duckdns addon and nginx addon installed but stop both before starting this docker. Please help. Thanks
Anyone manage to get WebSockets working correctly through this?
I just get authentication errors in the HA logs and nothing of use in the Proxy manager logs.
Hi All,
Im running this Addon for a while, but today my disk crashed. I restored a HA snapshot containing this addon, but got some troubles with the mariadb addon which I fixed by reinstalling the mariadb addon.
After that the Nginx PM was able to start again, but I could only logon using default credentials.
To my surprise my hosts configuration was still working, but it was not visible in the web UI ?!?
Is there a possibility to get my list of hosts back into the user interface?
Failed to renew certificate npm-2 with error: Some challenges have failed.
Challenge failed for domain nextcloud.mydomain.com
Failed to renew certificate npm-3 with error: Some challenges have failed.
Challenge failed for domain grocy.mydomain.com
Failed to renew certificate npm-6 with error: Some challenges have failed.
Challenge failed for domain rpi.mydomain.com
Failed to renew certificate npm-7 with error: Some challenges have failed.
mydomain.com is a placeholder for my real domain. But those 3 subdomains I don’t use anymore, they are not configured in NPM also… I have others… I checked the database of NPM also cant find them.
Challenge failed for domain wg.mydomain.com
Failed to renew certificate npm-14 with error: Some challenges have failed.
Challenge failed for domain npm.mydomain.com
Failed to renew certificate npm-16 with error: Some challenges have failed.
Challenge failed for domain nextcloud.mydomain.com
Failed to renew certificate npm-2 with error: Some challenges have failed.
Challenge failed for domain nextcloud.mydomain.com
Failed to renew certificate npm-3 with error: Some challenges have failed.
Challenge failed for domain grocy.mydomain.com
Failed to renew certificate npm-6 with error: Some challenges have failed.
Challenge failed for domain rpi.mydomain.com
Failed to renew certificate npm-7 with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-14/fullchain.pem (failure)
/etc/letsencrypt/live/npm-16/fullchain.pem (failure)
/etc/letsencrypt/live/npm-2/fullchain.pem (failure)
/etc/letsencrypt/live/npm-3/fullchain.pem (failure)
/etc/letsencrypt/live/npm-6/fullchain.pem (failure)
/etc/letsencrypt/live/npm-7/fullchain.pem (failure)
I don’t use DMSR but I think you might break the addon case it expects a different path for the backup folder. You can see the mapping in Portainer for each addon (for instance, these volumes are used by NPM).
Hi every day I get this message or when I am in different locations:
Login attempt failed Login attempt or request with invalid authentication from a0d7b954- nginxproxymanager.local.hass.io (172.30.33.8). See the log for details.
does anyone have an idea how i can fix this? thanks
Do you have this section in order to have secure connections to HA also from the other VLANs? I would suggest removing it and setting up NPM with basic HA connection; afterwards, if this works, it is only a matter of changing port and http to https of HA in NPM.
Why do you want to forward also port 81? If you want to access NPM from internet you can either setup a new subdomain (https://npm.your_current_address.org) or a subfolder (https://your_current_address.org/npm)
You only need ports 443>443 and 80>80 (both forwarded to NPM if not on the same machine as HA) or port 443>443 only if planning to use DNS Challenge.