Ultimate Starter - (PAGE 1) - Jellyfin, Jellyseerr, NZBGet, Torrents and *ARR Media Library Stack

Tutorial Ultimate Starter - (PAGE 1) - Jellyfin, Jellyseerr, NZBGet, Torrents and *ARR Media Library Stack 0.01

No permission to download

Currently reading
Tutorial Ultimate Starter - (PAGE 1) - Jellyfin, Jellyseerr, NZBGet, Torrents and *ARR Media Library Stack

Hello geekau, first of all I would like to thank you immensely for your tutorial, it was exactly what I needed, as I am inexperienced.
I have a Synology DS220+ and I'm trying to install via portainer, and the error appears after uploading the yaml and env. file ''failed to deploy a stack: 1 error(s) decoding: * error decoding 'Ports': Invalid ip address: http''
I have no idea which ip is wrong, I tried to simplify, trying only with gluetun and sonarr and I got the same error.

Hey @Diavolo, I'm re-developing this whole docker build and also the documentation, the early documentation is located at:


You can download all of the YAML files in the "Individual-app" directory, by going to GitHub - geekau/media-stack: Docker-Compose files and configs to build your desired media stack, quickly and easily. then selecting "<> Code" --> "Download Zip". Then you can extract all of the files from the "individual-apps" folder.

Then follow the README in the top link (individual-apps) and install them one at a time - Gluetun MUST be first. Then you can test each one as it loads.

The ENV file has changed slightly, there are only two folders, one for Docker configurations (use /volume1/docker) and one to contain all the media / downloads (use /volume1/data) or something similar.

If you continue to have issues with ports, it may be some of the ports numbers are already active on your system.

You can check active ports on Synology by running: sudo netstat -tulpn

You can then change all of the ports in the ENV file, so none of them conflict with anything which is currently running on your Synology.

Good luck mate.
 
Thanks for the reply, I downloaded the individual files and just tried gluetun to start with and got the same error as before.
I ran ''sudo netstat -tulpn'' and found no port conflict.
Anyway, I'll keep trying. I see that you are adding things in the tutorial, thanks for your patience.
 
Thanks for the reply, I downloaded the individual files and just tried gluetun to start with and got the same error as before.
I ran ''sudo netstat -tulpn'' and found no port conflict.
Anyway, I'll keep trying. I see that you are adding things in the tutorial, thanks for your patience.
Have you updated the following settings / variables to suit your system:

Code:
DOCKER_SUBNET=172.28.10.0/24
DOCKER_GATEWAY=172.28.10.1
LOCAL_SUBNET=192.168.1.0/24

VPN_SERVICE_PROVIDER=
VPN_USERNAME=
VPN_PASSWORD=
SERVER_REGION=

i.e. Have you put in your local LAN network details into "LOCAL_SUBNET" ? If these don't match your local system, then the Gluetun container will try to set up the network / VPN routing to a subnet which does not exist on your network.

Likewise, do you have an VPN account with an Internet service provider? i.e. NordVPN or PIA (Private Internet Access) etc... there are many out there which you can use, there is a link to some of the supported ones on Gluetun page:

Home · qdm12/gluetun Wiki <-- Check out the list of providers on the right hand menu.

There is also an issue with some Synology devices, which needs to have a kernel module installed, before Gluetun can create the VPN tunnel, check Quentin's wiki at:


Your NAS may need to have this workaround added, but there's great documented on the Gluetun wiki which should help you get that running.

I'm not sure if you're running the individual files via Portainer still, however you could also drop all of the individual-all compose files into /volume1/docker and then go there via SSH, and run the "sudo docker-compose up" command for Gluetun manually, then post the output back here if you're still having issues.
 
Yes, I changed to the following parameters:
DOCKER_SUBNET=172.20.0.0/16
DOCKER_GATEWAY=172.20.0.1
LOCAL_SUBNET=192.168.31.166

VPN_SERVICE_PROVIDER=nordvpn
VPN_USERNAME=***********
VPN_PASSWORD=***********
SERVER_REGION=Brazil

I think it's a silly mistake somewhere, I'll keep looking
 

Attachments

  • syno.jpg
    syno.jpg
    20 KB · Views: 29
LOCAL_SUBNET=192.168.31.166
^^^ This.

You've put in a single IP address, this should be a Subnet in CIDR format, as Gluetun uses it to route traffice between your local computer network, the VPN connection, and also the Docker network.

If your local network uses 192.168.31.1 - 254 (i.e. netmask is 255.255.255.0), then change this to 192.168.31.0/24 and try again.
Code:
LOCAL_SUBNET=192.168.31.0/24

With the updated ENV file at: media-stack/docker-compose.env at main · geekau/media-stack

You can put in your IP address into this setting:
Code:
LOCAL_DOCKER_IP=192.168.31.166

The LOCAL_DOCKER_IP setting gets used in the Jellyfin configuration when you enable DNLA, it adds the IP address to the JELLYFIN_PublishedServerUrl configuration, so local media devices / Smart TVs can connect to Jellyfin using the DNLA protocol.
 
Greetings geekau,
I hope you are well. I would like to thank you for the tutorial its appreciated. I know how much it takes to provide as much detail as possible.
The way service based stack environments are available now is very interesting, so I followed along without issue but it seems the UI for qbittorrent and SABnzbd has changed. plus the ports are different now in the env file.

Can you advise of the correct settings on below,
Transmission - Torrent Download Client:

Transmission connects to trackers, seeders and peers in the torrent network in order to access content which has been uploaded to torrent groups.

1. Open Transmissions Portal: http://localhost:9091

2. Press the "Spanner" icon in the bottom left corner to open "Preferences Menu"

3. Torrents Tab - Downloading to… Change this to: /data/torrents

I am not able to locate the setting for "Downloading to" Can you help?
1672481098294.png


NZBGet - Usenet Download Client:

1. Open NZBGet Portal: http://localhost:6789
  • Default Username: nzbget
  • Default Password: tegbzn6789
It seems the login requires Host server, is this correct?
1672481301284.png
Thank you for your help in advance.
 
Hello everyone, after weeks without touching this, I tried again, and I'm getting the following error message in the portainer: Error failed to create network media_network: Error response from daemon: Pool overlaps with another one on this address space. Following ChatGPT suggestion use these commands:
docker network ls
docker
network rm media_network
docker network create new_media_network


I was not successful, a message appears:
Got permission denied while trying to connect to the Docker daemon socket at uni ....
The apps appear in docker images but not in containers, and the network created exclusively for them in docker is empty, as are the persistent folders.
 
Please don't ask ChatGPT how to fix stuff on Synology, it doesn't know its a specialised OS, and has provided incorrect commands.

Try "sudo docker network ls" - you're on Synology and need to run as sudo for Docker commands.

The output error is saying the network pool overlaps with another address space, I would check Portainer network section to see what network addresses have been set up for bridge mode (media_network), and then change the address to something different in the docker-compose.env file.

Change these:
DOCKER_SUBNET=172.28.10.0/24
DOCKER_GATEWAY=172.28.10.1

To something different, like:
DOCKER_SUBNET=172.28.20.0/24
DOCKER_GATEWAY=172.28.20.1
 
@geekau You are Amazing for this setup!! Thank you soo much ahead of time.

I wanted to point out that there are a LOT of changes from this guide and the available yaml and ENV files on your Github.

I followed the guide to the T, but when I went to stand up the stack, I found that the directories you had us make in the guide were DEF not the same that were being requested by the YAML file.

I had about 6 different folders that just didn't exist and kept the stack from launching. AFter adding all those folders, I found that I kept getting another error when trying to start up the stack.

The error was something about the TUN not being available.

I was REALLY looking forward to this working, but after multiple hours of trial and error, I just gave up :-(

However, I really would like to get this going but just don't have the knowledge to do it. If you're still around, I'll happily provide the output error I get after getting everything as far as I did. Will wait to see if you respond back, and if so, I'll get to it!

Thanks again for everything that you put together. While it may not have worked for me, it was DEF a learning experience, one that I enjoyed :)
 
@geekau for someone that has tried a number of times to use Docker and failed this media guide was extremely helpful not just to get an automated *arr stack but to help me learn (some) docker. Thank you! I went to the new version (GitHub - geekau/media-stack: Docker-Compose files and configs to build your desired media stack, quickly and easily.) but I see that the mediastack.guide website doesn't seem to have any instructions. Is there an updated site for this? Also I have run into issues (mostly I'm sure b/c i'm a total docker noob) adding some apps (SABnzbd, qBittorent, Tdarr and Unpackerr) to the docker-compose.yaml file, I keep getting various errors (mostly missing variables in the configs folder.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top