PostgreSQL Updates AFAIK require manual Backup / Restore of the Database. But better look that up. I think the last one I did was:
As I said, better look it up first, this is just how I remember the process (but not the backup / restore commands).
On mobile atm. Look for pi-hole + unbound. Uses root DNS. Might take a tiny bit longer to resolve at first, but as long as root DNS is uncensored it should be the way to go.
I posted it yesterday, but just in case we are facing some Fediverse cross-instance sync issue, here is what I posted. Sorry again if this is not for you then :-( Quote: I am very sorry, as I have just realized that it is only available in a single Language: German. I fear the chances are pretty low that it is of use for you, but maybe for the other German around here in the Fediverse... https://www.willuhn.de
Thank you very much! Little did I know! I will look for alternatives now... MeshCentral is the next on my list I guess.
I use Hibiscus for all my banking needs.Makes a direct connection to my bank. Will get you the link if there is interest when I am back home.
What is your issue with Rustdesk? I would understand if you mention Teamviewer, which runs through 3rd party servers, but Rustdesk? Is the client phoning home despite self-hosting or what do you mean? I am seriously interested.
On the other hand, I would not use RDP over the Internet without a VPN or at least an RDP Gateway in between both parties.
I spent half a day trying to get acme-dns + Cert Warden up and running and failed miserably. And I think I will give up on it. That does not happen usually, but during my debugging sessions I have seen that the acme-dns project is not maintained regularly since quite a while. The current maintainer just has not enough time, but tries to prepare the project for a move to a new GitHub organization, so more people can help with the project. Until then, Issues and PRs accumulate, so I am not sure anymore if I should stick to acme-dns or just do it differently.
Why did I pick this scenario? Because of Let's Encrypt certificates and my DNS provider does not allow fine-grained API Keys for DNS management. This means, that currently the processes that request certificates in my Network need the API Key for the dns-challenge for Let's Encrypt.
Ways around that are by either using Let's Encrypt alternate (I think it is called DNS alias mode) method where you can request Certificates for your main domain, but put the TXT records for the DNS challenge on another Domain. One way is to just use a 2nd Domain for that if you have one.
I tried to do it with a Subdomain of my Main Domain that I delegate to acme-dns. The whole acme-dns, Domain delegation stuff etc. works fine, but I am not able to get this hooked up to Cert Warden properly and end up with error messages that make no sense to me and since I do not find any further information in the logs, as I said, I just gave up yesterday evening... for now ;-)
Another thing I am struggling sometimes is my Pi-Hole + Unbound setup where Unbound for no reason just returns a NXDOMAIN for some queries and I can not figure out why, under which circumstances and when that happens. It just seems to be random and a restart / cache clearing etc. does not fix it.