I just update. If it breaks, I read the notes. Probably the wrong way but it worked. And I use it for a long time.
To me, it was never that unstable. And since a couple of months it's very stable.
Backup first.
I've got the same problem since a month or two with another dyndns provider. That's not specific to the dydns provider. It is the router. Yet I have no idea how to fix it, and I am too lazy currently.
I run nextcloud on my machine. If there's a crack, there would be one in their hosted instance as well. There's nothing really I can do about security of it.
As you said, a free post is better than paid ads somewhere else. And you don't use it personally, that's the great part. Moreover, you use lemmy. Kudos to you
Sorry for not having expressed what I did.
I wrote a podman compose file, pulled the caddy image, wrote a caddyfile, started it and tried to connect to a service via subdomain.domain.tld .
The caddyfile contains my http and tls ports and the domain and ip for the reverse proxy routing according to the docs.
The result is no log entry in caddy and no result in the browser or curl.
Thanks! I use wake on lan with rtcwake to boot at a certain time. I also found an app via which I can boot the server via wake on lan. But it would be nice if it could wake up just by requesting the service
I just update. If it breaks, I read the notes. Probably the wrong way but it worked. And I use it for a long time. To me, it was never that unstable. And since a couple of months it's very stable. Backup first.