This is how I set up my reverse proxy and it works really well with wildcard SSL certs. Only need one certificate for as many sites as I want!
This is how I set up my reverse proxy and it works really well with wildcard SSL certs. Only need one certificate for as many sites as I want!
Well how was I supposed to figure out that my docker node running on libreelec won’t connect to the swarm because the kernel was compiled with out the The Berkeley Packet Filter protocol.
And now I will think of beer when ever I forget my local IP address.
I’ve never seen this particular error, but CPU stall warnings seem like a fairly common thing. I wouldn’t jump straight to hardware fault, but it’s a possibility.
Well this makes me feel better about my stupid questions on stack overflow.
I followed this guy’s tutorial: https://www.youtube.com/watch?v=liV3c9m_OX8
You do need your own domain name but I got one on namecheap for like $15 per year. It’s worth it.
Looks cool dude. Have you tried using Traefik on docker? You can name your service like https:// homeassistant.thanatos instead of 192 .168.1.1:8080.
It’s pretty cool and it can even handle SSL certs.
I haven’t tried caddy but I’ve heard good things. I’ve used nginx in the past. I’m currently using Traefik and have been for a few years now. Once it’s set up its pretty great.