Skip to content

Commit

Permalink
Merge pull request #5881 from nextcloud/enh/noid/add-jellyfin
Browse files Browse the repository at this point in the history
fail2ban-cc: add jellyfin
  • Loading branch information
szaimen authored Jan 16, 2025
2 parents 784da23 + 276cd7d commit c19ba34
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 1 deletion.
5 changes: 5 additions & 0 deletions community-containers/fail2ban/fail2ban.json
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,11 @@
"source": "nextcloud_aio_vaultwarden_logs",
"destination": "/vaultwarden",
"writeable": false
},
{
"source": "nextcloud_aio_jellyfin",
"destination": "/jellyfin",
"writeable": false
}
]
}
Expand Down
2 changes: 1 addition & 1 deletion community-containers/fail2ban/readme.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
## Fail2ban
This container bundles fail2ban and auto-configures it for you in order to block ip-addresses automatically. It also covers https://github.com/nextcloud/all-in-one/tree/main/community-containers/vaultwarden, if installed.
This container bundles fail2ban and auto-configures it for you in order to block ip-addresses automatically. It also covers https://github.com/nextcloud/all-in-one/tree/main/community-containers/vaultwarden and https://github.com/nextcloud/all-in-one/tree/main/community-containers/jellyfin, if installed.

### Notes
- If you get an error like `"ip6tables v1.8.9 (legacy): can't initialize ip6tables table filter': Table does not exist (do you need to insmod?)"`, you need to enable ip6tables on your host via `sudo modprobe ip6table_filter`.
Expand Down
1 change: 1 addition & 0 deletions community-containers/jellyfin/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ This container bundles Jellyfin and auto-configures it for you.
- 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!
- If you want to secure the installation with fail2ban, you might want to check out https://github.com/nextcloud/all-in-one/tree/main/community-containers/fail2ban
- 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.

Expand Down

0 comments on commit c19ba34

Please sign in to comment.