Skip to content

Route Plexio traffic through gluetun VPN proxy to bypass provider IP block#1

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/troubleshoot-plexio-connectivity
Draft

Route Plexio traffic through gluetun VPN proxy to bypass provider IP block#1
Copilot wants to merge 2 commits intomainfrom
copilot/troubleshoot-plexio-connectivity

Conversation

Copy link
Copy Markdown

Copilot AI commented Mar 3, 2026

VPS IP appears blacklisted by Appbox provider after disclosing Plexio usage. Direct Plex access works from home IP; Plexio fails from all locations — classic server-side IP block.

Changes

  • apps/plexio/compose.yaml: Added depends_on: gluetun with health check gate, matching existing tweakio pattern
  • apps/plexio/.env: Added HTTP_PROXY/HTTPS_PROXY pointing to http://gluetun:8080 (gost HTTP proxy running in gluetun's network namespace)

Why proxy env vars over network_mode: service:gluetun

Plexio needs its own network namespace for Traefik label discovery and healthcheck routing. Standard Python HTTP libraries (requests, httpx, aiohttp) all respect HTTP_PROXY/HTTPS_PROXY, so outbound requests get tunneled while inbound access stays intact.

Warp alternative

Documented in .env comments — swap to socks5://warp:1080 and enable the warp profile if preferred over gluetun.


🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Co-authored-by: RenewedKeys <75775165+RenewedKeys@users.noreply.github.com>
Copilot AI changed the title [WIP] Troubleshoot connectivity issue with Plexio Docker container Route Plexio traffic through gluetun VPN proxy to bypass provider IP block Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants