Maybe someone can explain this to me, I am a bit confused…
I am trying to get ngnix proxy manage add-on to work. When I first started it, it wouldn’t start complaining “Bind for 0.0.0.0:443 failed: port is already allocated”. When I checked to see who is using 443 it was the SSL proxy. So I stopped the proxy, which made it possible for me to start the manager. However, since the proxy is not running, the manager can’t access port 81.
I think I am missing something… Any advice on where to look?
Did you ever figure this out? I am running into the same issue
I recently encountered the same problem. It has been working fine for many months. I’m not sure because I had tried let’s encrypt for my other virtual host on my apache ubuntu.
did you solve?
Having the same error, I do not know how to check in HASSIO who is using port 443
Recieve also this error not sure is related
20-03-31 16:10:28 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 16:10:28 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 16:10:28 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-31 16:10:28 INFO (SyncWorker_3) [supervisor.docker.interface] Clean hassio_dns application
20-03-31 16:10:29 INFO (SyncWorker_3) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3
20-03-31 16:10:48 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 16:10:48 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 16:10:48 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
So what I found out is, that one can check the ports by shh into HA and running the following command: sudo netstat -tulpn | grep LISTEN. There you could find every port used.
Unfortunately I am running into the same issue as you @bkahn I even started a new topic here
Did anyone of you found a solution?