this post was submitted on 05 Apr 2024
6 points (100.0% liked)

Selfhosted

46677 readers
277 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
6
known proxy for jellyfin in container? (lemmy.ml)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
7 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?

all 9 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 1 year ago

That setting also takes host names. As long as both containers share at least one network, put in the service name (not the container_name!), e.g. "npm" or whatever yours is called and you should be fine.

[–] [email protected] 1 points 1 year ago

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
IP Internet Protocol
Plex Brand of media server package
VPN Virtual Private Network

[Thread #674 for this sub, first seen 11th Apr 2024, 20:55] [FAQ] [Full list] [Contact] [Source code]

[–] [email protected] 1 points 1 year ago (1 children)

Put them on different subnets and use the gateway IP address maybe?

[–] [email protected] 1 points 1 year ago

When using a different subnet, the requests come from

[16:27:24] [INF] [35] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 10.89.2.6 request