So I've seen that quite a few are already running Emby in a Kubernetes Cluster.
My setup currently looks like this:
- One Kubernetes Node (I'm using K8s because I'm familiar with it and I like writing deployment-manifests :-) )
- A standard router from my ISP, doing port-forwards on HTTP & HTTPS
- MetalLB assigning virtual IPs for loadbalancers (L2)
- Nginx Ingress using a LoadBalancer, so it gets a virtual IP. uses Service with `externalTrafficPolicy: local`.
- Emby using an Ingress-Resource, HTTPS, letsencrypt certificates.
My issue though is that it seems like Emby considers everything to be the "local" network.
From skimming through the logs:
2019-11-05 19:40:11.692 Info HttpServer: HTTP GET http://<mydomain>:8096/emby/Users/<key>. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.2 Safari/605.1.15
2019-11-05 19:40:11.695 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 3ms. http://<mydomain>:8096/emby/Users/<key>
A few things:
My Emby instance is not reachable under http://<mydomain>:8096, but rather on https://<mydomain>:443 (through the Ingress).
It seems like Emby responds to the request to localhost??
This would explain why Emby considers everything to be local network.
Anybody an idea why?
Or what did you guys set to actually pass through the Source IP?
Like mentioned before, I'm already using `externalTrafficPolicy: Local` for the nginx-ingress service.
Also, for reference, the deployment yaml:
- name: emby-server
- name: "UID"
value: "1030" # emby user
- name: "GID"
value: "1111" # share group
- containerPort: 8096
- mountPath: /config
- mountPath: /mnt/media
- name: emby-media
- name: emby-config
Total noob with emby, deployed it a couple of days ago.
Any help would be appreciated.