kerstenremco
commented
16 hours ago As far as I understand the 443 port should serve the default site? Since it cannot be accessed I believe this is causing other issues, such as obtaining ssl certs from letsencrypt, and in the off chance the ssl certificate generation does succeed, I get 400 errors when trying to access the host.
That's correct. But the "default site" doesn't provide a SSL certificate, that's why curl throws this error. So you'll need to setup a proxy host to HA, and bind a SSL certificate to that hostproxy.
ReenigneArcher
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
I am attempting to migrate from the HomeAssistant plugin version (it's broken and there's no way to upgrade without losing all info) of this over to this standalone version. After following the basic example in the readme, I can access the config UI, the site at
http://<ip>:80, but I cannot access the site athttps://<ip>:443.I am using portainer, and Ubuntu server 24.04, with bridge networking. I can't use host networking because the container tries to use port 3000, but that's already in use on the host (probably by portainer itself). Port 443 is not used by the host at all, and the issue persists if I remap the container's 443 to another port, such as 4443.
As far as I understand the 443 port should serve the default site? Since it cannot be accessed I believe this is causing other issues, such as obtaining ssl certs from letsencrypt, and in the off chance the ssl certificate generation does succeed, I get 400 errors when trying to access the host.
There is probably something simple that needs to change on my host, but I have no idea what that could be and have been searching the documentation, discussions, and issues for hours without success.
If it's helpful, here are the full logs.
Nginx Proxy Manager Version
v2.12.1
To Reproduce Steps to reproduce the behavior:
Expected behavior
https works
Screenshots
Operating System
Ubuntu server 24.04 with portainer v2.21.4 community edition
Additional context