2024-12-08, 03:43 PM
Yes, i do expose ports (8086, udp and tcp 1900, 7359 as in my first post described.)
I have to do this to use jellyfin with my local ip for my tv. (If not, a request from tv would have to use my domain which in return would be an external request.)
So yes, i do expose ports and put the docker-bridge ips in the input field.
I can confirm now, that it is working, but this is what i had to do:
172.18.0.0/16, 172.16.0.0/12, 192.168.178.50/32
-> without adding the subnet it will not work in my setup!
as you can see i use the docker-traefik ips and the real ip of the raspberry-pi as known-proxy list.
Now it correctly can detect external/internal ip-addresses.
It would be nice when the text for configuration would reflect that.
And, if as you said, hostnames aren't supported at all, it shouldn't state that in the description.
Hope this helps!
I have to do this to use jellyfin with my local ip for my tv. (If not, a request from tv would have to use my domain which in return would be an external request.)
So yes, i do expose ports and put the docker-bridge ips in the input field.
I can confirm now, that it is working, but this is what i had to do:
172.18.0.0/16, 172.16.0.0/12, 192.168.178.50/32
-> without adding the subnet it will not work in my setup!
as you can see i use the docker-traefik ips and the real ip of the raspberry-pi as known-proxy list.
Now it correctly can detect external/internal ip-addresses.
It would be nice when the text for configuration would reflect that.
And, if as you said, hostnames aren't supported at all, it shouldn't state that in the description.
Hope this helps!