errantp

Hello, I have spent a few hours reading and thinking about this and wanted to see if anyone has any suggestions. I have an A record pointing to the tailacale IP of an container which is great but the two things I have been trying to solve is how to get https working for that like the ts.net URL. Also I would like to have the domain resolve to the internal IP at home. I think I could just run a different DNS intentionally, but not clear on how would handle the tls. Since just using tailacale in the containers doesn't seem like I need a reverse proxy. Any suggestions? My domain is registered with cloudflare if that helps.

Seems to have been the macvlan bug, all seems stable now.

After some thought it is probably related to macvlan and the bro since that was also the first container I had that wasn't using br0 network which sounds a lot like my symptoms. Keeping Docker disabled for a couple of days and will go from there.

Okay, the server became non responsive over the night. I have disabled Docker so that Parity can finish and also syslog. Maybe there is a hardware issue.

Sounds, good. I wasn't sure if I should post the before or after. When it crashes again (though hopefully with any luck) I will post the logs. Thanks!

Hello, I recently upgrades my server which was mostly an overall except for the storage drives and adding the NVME disk as a newer and large cache. Things seem to be working generally but last couple of days the Docker containers stop working, and if I try to re-enable. Docker it says Docker service failed to start. I did file system tests and scrubs without finding any issues. I was wondering if anyone had an idea. unraid-diagnostics-20240602-1621.zip

I was having this problem earlier, it turns out there was a leading space at the start of the token from when I copied the token from duckdns. When I removed the leading space everything worked.