From fc0fde93b54bc2e192fae1e50c9195166876d1fd Mon Sep 17 00:00:00 2001 From: Simon L Date: Wed, 3 Apr 2024 13:16:50 +0200 Subject: [PATCH] add some more infos to jellyfin and plex Signed-off-by: Simon L --- community-containers/jellyfin/readme.md | 2 ++ community-containers/plex/readme.md | 1 + 2 files changed, 3 insertions(+) diff --git a/community-containers/jellyfin/readme.md b/community-containers/jellyfin/readme.md index 5292928b96a..f744069b9ac 100644 --- a/community-containers/jellyfin/readme.md +++ b/community-containers/jellyfin/readme.md @@ -5,8 +5,10 @@ This container bundles Jellyfin and auto-configures it for you. - This container is incompatible with the [Plex](https://github.com/nextcloud/all-in-one/tree/main/community-containers/plex) community container. So make sure that you do not enable both at the same time! - This container does not work on Docker Desktop since it needs `network_mode: host` in order to work correctly. - After adding and starting the container, you can directly visit http://ip.address.of.server:8096/ and access your new Jellyfin instance! +- This container should usually only be run in home networks as it exposes unencrypted services like DLNA by default which can be disabld via the web interface though. - In order to access your Jellyfin outside the local network, you have to set up your own reverse proxy. You can set up a reverse proxy following [these instructions](https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md) and [Jellyfin's networking documentation](https://jellyfin.org/docs/general/networking/#running-jellyfin-behind-a-reverse-proxy), OR use the [Caddy](https://github.com/nextcloud/all-in-one/tree/main/community-containers/caddy) community container that will automatically configure `media.$NC_DOMAIN` to redirect to your Jellyfin. - ⚠️ After the initial start, Jellyfin shows a configuration page to set up the root password, etc. **Be careful to initialize your Jellyfin before adding the DNS record.** +- If you have a firewall like ufw configured, you might need to open all Jellyfin ports in there first in order to make it work. Especially port 8096 is important! - The data of Jellyfin will be automatically included in AIO's backup solution! - See [here](https://github.com/nextcloud/all-in-one/tree/main/community-containers#community-containers) how to add it to the AIO stack. diff --git a/community-containers/plex/readme.md b/community-containers/plex/readme.md index a3f679ccc78..c9553645b7d 100644 --- a/community-containers/plex/readme.md +++ b/community-containers/plex/readme.md @@ -5,6 +5,7 @@ This container bundles Plex and auto-configures it for you. - This container is incompatible with the [Jellyfin](https://github.com/nextcloud/all-in-one/tree/main/community-containers/jellyfin) community container. So make sure that you do not enable both at the same time! - This is not working on arm64 since Plex does only provide x64 docker images. - This is not working on Docker Desktop since it needs `network_mode: host` in order to work correctly. +- This container should usually only be run in home networks as it exposes unencrypted services like DLNA by default which can be disabld via the web interface though. - If you have a firewall like ufw configured, you might need to open all Plex ports in there first in order to make it work. Especially port 32400 is important! - After adding and starting the container, you need to visit http://ip.address.of.server:32400/manage in order to claim your server with a plex account - The data of Plex will be automatically included in AIOs backup solution!