Guadin

I had a task running which would scan all incoming calls on all SIM cards. It then checked the numbers for known contacts and if they are unknown it would check if they called multiple times. I made it because I was bothered by a lot of spam/scam callers. This task would block all notifications, vibrations and ringtones. So it didn't bother me at all that they called.

Indeed. The front ends could be less or more "secure"/private. And by that I mean that I don't know how the app themselves are with access and your data. So I don't know if they collect and share any data and how reliable the developers are.

Indeed. Or otherwise Island as an alternative. Don't know how those two compare on the security and privacy front.

You can put it in a work profile and trust that Android is protective enough to keep your data safe and access limited. Otherwise buy a second phone just to put WeChat on it. Don't know how WeChat works, but if it's like Whatsapp then you don't need to bother with a secondary number.

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.

What does the NGINX proxy manager do? Is that to access the mediaserver?

Well they don't ignore that market. They decided to not sell there yet. Because going to a new large market far away from all your warehouses and with a potential large demand cause a lot of headaches. Not to mention all the regulations and rules they need to abide by.