Thanks, that’s good to know. Going to update it right away, hopefully this will solve my problem.

That looks nice. Added it to my list to look at. Thanks.

You’ve got a good point with Home Assistant. I have automations setup so that I barely have to do anything manually. So I almoat forget that Home Assistant runs quite a lot in my home. And especially in the beginning it was nice to setup but not really needed. Know it is needed.

I didn’t know if this was something I was missing, but man this could be my new number 1. The import function is really great. I’ve already added a lot of recipes. Thanks!

I’ve installed it as well but the blackout/redact feature didn’t work as expected…So not sure if it will be that useful for me. But since I ditched Adobe, I now at least have a PDF editor.

You’ve just made me waste the next 2 days, because this sounds great! Only thing I’m a bit hesitant about is trusting all bridge makers. I’m a bit more aware that I use a lot of FOSS where it could be easy for the dev’s to just go rogue. But that’s still better than giving it away to some closed source company.

Looks really great. I’m depending on Synology for CalDav and WebDav but if I can move away from that to make switching NAS in the future easier, that would be great.

In that case, enjoy! It’s a great feeling when you get it working.

If you’re going to do it on your synology, see if you need to fix the TUN error. Also, you need to add ip routes to your synology to have the IP’s from your VPN on docker forwarded to docker. Make sure these are persistent or added on every startup.

Make sure you allow the VPN to work by adding it to the synology firewall.

You need to setup port forwarding on your router. It needs to point to your synology to the port which is linked to the docker container. You also need to add the route to your router to be able to access your network. For instance, if your VPN has 10.0.3.* and your LAN uses 10.0.0., your LAN/router won’t know where to send the response packets to the VPN network. So when connected to your VPN you will never be able to load stuff. If you add that 10.0.3. needs to route to your synology, and your synology knows that range needs to be routed to the Docker VPN container everybody knows where it needs to go.

Tailscale is (like) a VPN, but traffic will go through their servers. If you setup your own VPN server then traffic will remain between your client and your own server.

Did you setup port forwarding and routing tables when you installed your VPN server?.

The Synology VPN package is lacking behind a lot, so you could be missing some security updates.

If you use a VPN to hide your services, you reduce your attack/risk. Since there is only one package/software suite which could’ve vulnerabilties. And VPN’s are focussed on security. If you expose all your hosted stuff, all those programs need to be secure to prevent abuse. And not everybody is as skilled to build it securily.

I would recommend, for you, to use something like tailscale. Since you seem like someone at the beginning of their safety journey. With setting up a VPN server, you need to know a little bit what your doing to make it secure and work. And you could invest time to learn it all, or you could use something that does it for you. Another, not so wise, advise could be to use a docker container to host the VPN. Most containers have all settings correctly setup and have guides to make it secure. But that means you don’t know what you installed and that could be a bad thing as well. Furthermore, docker adds to the complexity of making it work.

Didn’t Elon say he hated the login-window-on-scroll just after purchasing twitter?

Yeah that sounds about enough to handle the load. How many workers do you use? And do you see any errors in your logs about handling messages? You could try to search for that particular thread to see if all replies are handled correctly?

Does your server have enough power and workers to handle all the federated messages? Or is it constantly at 100% CPU?