Selfhosted

40152 readers

609 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

known proxy for jellyfin in container? (lemmy.ml)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

10 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 7 months ago (2 children)

It may not affect this current use case for a home media server, but people should still be aware of it so as they learn and grow, they don’t paint themselves in a corner by knowing only the anti patterns as the path forward.

[–] [email protected] 4 points 7 months ago

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.

[–] [email protected] 2 points 7 months ago

I'm glad you commented as I didn't know I can define 2 networks in Docker. At the moment I'm trying to get Arr working in docker and it was going well until I realised my containers can't communicate with Plex. I believe it's because I'm using Gluetun and I haven't enabled LAN networking on my VPN. but theoretically the apps that need to see Plex don't need to be behind the VPN, but they didn't work when they weren't because they couldn't talk to Prowlarr.

So theoretically I could just slap "bridge" in my network as well, and then they'll be in Gluetun and out of it at the same time.

I may try it tomorrow. Thanks for your comment