💾 Archived View for ilonagabor.de › posts › degoogle.gmi captured on 2021-12-05 at 23:47:19. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
So, today I took a big step to make my browsing habits safer. I have been using self-hosted searx instead of google/DuckDuckGo and Invidious to watch YouTube content for quite some time. However, the fact that me and my immediate family are the only users on the private instance was always a sore spot, since Google can still track our search habits through my server's IP-address. It is still a lot better than viewing the content directly on their sites (cookies etc.) but a long way from complete privacy.
I came up with a server-side solution to route all the traffic from searx and Invidious through my VPN provider, NordVPN using the Wireguard protocol. Though it took a bit of figuring out, the setup now works, with very good response speeds. I confirmed that no packets are being sent to Google or YouTube by sniffing my server traffic with Wireshark.
If you are interested in this setup I am including the docker-compose file here.
Prerequisites:
- A computer running Docker & Docker Compose
- A NordVPN account
git clone https://github.com/iv-org/invidious docker-compose build
docker-compose up -d
This will also pull the searx and bubuntux/nordvpn docker images and bundle everything together. All containers should connect through the "vpn" service, the trick here is this:
network_mode: service:vpn
which I added to each service.
After this is done, enjoy on your client computer (localhost:3000 for Invidious, localhost:8080 for searx). If you are on a server, you can set up reverse proxies with nginx or Apache and obtain an SSL-certificate from LetsEncrypt and then use your instances on their own dedicated subdomains from anywhere you are.
Last updated: 31 Jul 2021 23:35:35 CEST