I’ve got jellyfin and nginx proxy manager running in two separate containers. What do I need to specify in known proxies? The ip is changing frequently which means I can’t use it.
I try setting the ip in the compose file but something is wrong. nginx proxy manager:
22 networks:
23 npm:
24 ipv_address: 172.20.0.2
25
26 networks:
27 npm:
28 driver: bridge
29 ipam:
30 config:
31 - subnet: 172.20.0.0/24
32 gateway: 172.20.0.1
33
and
jellyfin:
32 networks:
33 npm:
34 ipv_address: 172.20.0.3
35
36 networks:
37 npm:
38 driver: bridge
39 ipam:
40 config:
41 - subnet: 172.20.0.0/24
42 gateway: 172.20.0.1
jellyfin log:
[16:08:01] [INF] [16] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 172.20.3.11 request
can someone point me into the right direction?
as someone who does stuff in my lab that can translate to a work context, i absolutely second this opinion.
if i am labbing to learn, then learning the best way to do it is always be the main focus, even if it means restarting what I was doing to change how some prerequisite is setup or functions.
today, OP is working with jellyfin, but as an example, what happens if later they get security cameras and want to use some sort of local ML to analyze events, and don’t want to put a lot cpu utilization to that task during lulls in activity? a solution might be to dynamically create and destroy containers for the analysis tasks, and the background on a network setup in an unrelated container stack that would allow scaling that means one less problem to solve later.