Skip to content
This repository has been archived by the owner on Jul 16, 2023. It is now read-only.

Deployed to Kubernetes, unable to connect to UI #151

Open
GoingOffRoading opened this issue Jan 28, 2023 · 0 comments
Open

Deployed to Kubernetes, unable to connect to UI #151

GoingOffRoading opened this issue Jan 28, 2023 · 0 comments

Comments

@GoingOffRoading
Copy link

GoingOffRoading commented Jan 28, 2023

In Kubernetes, clients connect to services over the Kubernetes network range (example CIDR 10.244.0.0/16).

So the journey my local machine takes to connect to the docker-qbittorrentvpn is (all numbers are hypotheticals):

  • My machine: 192.168.1.110
  • Kubernetes Server Node: 192.168.1.250
  • Kubernetes Service Network IP in the Kubernetes Server Node: 10.103.253.51
  • Kubernetes Service Network Port: 30325
  • Container Port: 8080

Setting the docker-qbittorrentvpn LAN_NETWORK variable as both CIDRs does not make local access possible. Example:

        - name: LAN_NETWORK
          value: "10.244.0.0/16,192.168.0.0/24"

Browser gets a "This site can not be reached" when trying the correct IP:port.

There's nothing in the logs about failed site access.

However if I access docker-qbittorrentvpn from a reverse proxy (Traefik), access is perfect.

Any ideas on how to fix the local access?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant