{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiakor7tjoo6gtfxftdnrgwno2lnaof464wzssh5f4ybnmhhtt55ti",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mnzi5ewpxyn2"
  },
  "path": "/t/is-this-really-how-self-hosting-front-ends-works-going-between-lan-and-vpn-connection/38462#post_4",
  "publishedAt": "2026-06-11T14:33:33.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "(click for more details)"
  ],
  "textContent": "If you look separately at the connection between your pc and searxng and the connection between searxng and the internet it becomes more clear. Your pc connects to your server → docker network → gluetuns network → searxng. Then searxng connects to the internet and since it (likely) has `network_mode: service:gluetun` in the compose file their only way to connect to the internet is through the gluetun VPN and your Home IP will not be used. Then it sends its results back to your pc via the local connection (as long as firewall rules are correct etc.)\n\nBe aware that the sites you visit will be visited with your real IP. Only your search is proxied through searxng and the vpn. As soon as you click on a search result your pc will connect to that site directly with your Home IP if it doesn’t have it’s own VPN running.\n\nNot really sure (click for more details)",
  "title": "Is this really how self-hosting front ends works going between LAN and VPN connection?"
}