Haha! I feel like I got a little roasted and have some learning to do, but this hobby is all good fun.
I’m definitely not hating on docker. I use it for dozens of containers across several machines and love how easy it is, and even some of the fights we’ve had. If that works for people’s needs, awesome!
I really wish I remembered what the error was. It’s been bugging me all day. Maybe it’s not a thing anymore.
It was many, many years ago, but if I recall some of the add-ons or installations didn’t work in the docker version. I started with docker on a Synology server, but I gave up on the whole project for a year until I found a Pi in a drawer I forgot I had.
HAOS just feels more “complete” to me.
That’s what home assistant is built to do. There is a docker version, but I hit limits pretty quick and fired up an old raspberry pi running HomeassistantOS
One app, many devices & brands, custom interfaces for each member.
Ah, certbot might be a little different then my system. Mine begins the process of renewing the let’s encrypt cert on port 80 and switches to 443 to finish. I have to have both open.
Http is port 80, but https is port 443. I’d try opening that too.
Some modems have DHCP on by default so there is a second firewall that needs to be disabled.
WAN -> modem with DHCP -> router with DHCP.
At least for Comcast, there is a option to disable NAT/Firewall in case you have your own hardware. Some modems on networks like AT&T can’t disable it if I recall.
Woooow totally spaced. You know all that hahaha!
Could someone please ELI5 that script. I’m all for keeping things clean, but old enough to remember the days of console based trolling.
I run mine behind a reverse proxy too and had to do that as well. Seems like a common thing there should be a system config for.