Easy Automated Home Media Server errors

dregus · 26. März 2021

I have tried googling a solution for the errors I'm receiving after deploying this stack. I've changed and updated just about every Env value and still the same errors. Any help would be greatly appreciated.

_vpnstack_transmission-openvpn_1_logs (1).txt

Code

version: '2.1'
services:
 transmission-openvpn:
    volumes:
        - /srv/dev-disk-by-uuid-FE56865F56861893/downloads:/media/downloads
        - /srv/dev-disk-by-uuid-FE56865F56861893/appdata/docker/:/data
        - /srv/dev-disk-by-uuid-FE56865F56861893/appdata/docker/:/config
        - /etc/localtime:/etc/localtime:ro
    environment:
        - PUID=1000
        - PGID=100
        - CREATE_TUN_DEVICE=true
        - OPENVPN_PROVIDER=NORDVPN
        # - OPENVPN_CONFIG=default
        - NORDVPN_COUNTRY=US
        - NORDVPN_CATEGORY=legacy_p2p
        - NORDVPN_PROTOCOL=tcp
        - OPENVPN_USERNAME=DONT_SHARE_THIS
        - OPENVPN_PASSWORD=DONT_SHARE_THIS_EITHER
        - OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60
        - WEBPROXY_ENABLED=false
        - LOCAL_NETWORK=192.168.1.0/24
        - TRANSMISSION_SCRAPE_PAUSED_TORRENTS_ENABLED=false
        - DNS=8.8.8.8,8.8.4.4
        - GLOBAL_APPLY_PERMISSIONS=false
    cap_add:
        - NET_ADMIN
    logging:
        driver: json-file
        options:
            max-size: 10m
    ports:
        - 9091:9091
        - 9117:9117
        - 7878:7878
        - 8989:8989
        - 8686:8686
        - 5299:5299
    restart: always
    image: haugene/transmission-openvpn
 
 jackett:
    image: linuxserver/jackett
    container_name: jackett
    network_mode: "service:transmission-openvpn"
    environment:
        - PUID=1000
        - PGID=100
        - TZ=America/Los_Angeles
        - AUTO_UPDATE=true #optional
        - RUN_OPTS=#optional
    volumes:
        - /srv/dev-disk-by-uuid-FE56865F56861893/appdata/jackett:/config
        #Jackett only needs config
    restart: unless-stopped
 
 radarr:
    image: linuxserver/radarr
    network_mode: "service:transmission-openvpn"
    container_name: radarr
    environment:
        - PUID=1000
        - PGID=100
        - TZ=America/Los_Angeles
        - UMASK_SET to UMASK #optional
    volumes:
        - /srv/dev-disk-by-uuid-FE56865F56861893/appdata/radarr:/config
        - /srv/dev-disk-by-uuid-FE56865F56861893/media:/media
    restart: unless-stopped
 
 sonarr:
    image: linuxserver/sonarr
    network_mode: "service:transmission-openvpn"
    container_name: sonarr
    environment:
        - PUID=1000
        - PGID=100
        - TZ=America/Los_Angeles
        - UMASK_SET=022 #optional
    volumes:
        - /srv/dev-disk-by-uuid-FE56865F56861893/appdata/sonarr:/config
        - /srv/dev-disk-by-uuid-FE56865F56861893/media:/media
    restart: unless-stopped
 
 lidarr:
    image: linuxserver/lidarr
    network_mode: "service:transmission-openvpn"
    container_name: lidarr
    environment:
        - PUID=1000
        - PGID=100
        - TZ=America/Los_Angeles
        - UMASK_SET=022 #optional
    volumes:
        - /srv/dev-disk-by-uuid-FE56865F56861893/appdata/lidarr:/config
        - /srv/dev-disk-by-uuid-FE56865F56861893/media:/media
    restart: unless-stopped
 
 lazylibrarian:
    image: linuxserver/lazylibrarian
    network_mode: "service:transmission-openvpn"
    container_name: lazylibrarian
    environment:
        - PUID=1000
        - PGID=100
         - TZ=America/Los_Angeles
        #- DOCKER_MODS=linuxserver/calibre-web:calibre #optional
    volumes:
        - /srv/dev-disk-by-uuid-FE56865F56861893/appdata/lazylibrarian:/config
        - /srv/dev-disk-by-uuid-FE56865F56861893/media:/media
    restart: unless-stopped

Alles anzeigen

KM0201 · 26. März 2021

1. Under transmission-openvpn... you have your data directory and your /config directory going to the same path.. Is that right? On mine, /data is where downloads go, etc. (I don't have a /downloads)

2. It looks like it's asking for a vpn configuration file... did you put the appropriate vpn file in place?

KM0201 · 26. März 2021

Wait, I just looked at your compose again.. Why do you have a # sign in line 14? You are making it essentially skip that line.

dregus · 26. März 2021

Zitat von KM0201

Wait, I just looked at your compose again.. Why do you have a # sign in line 14? You are making it essentially skip that line.

I was just following Techno Dad's tutorial.

Frepke · 26. März 2021

You better change your VPN credentials now you've exposed them to everyone

KM0201 · 26. März 2021

OP I removed your personal info from your docker-compose, but I'd agree w/ the above... not sure how many have seen it so you need to change your VPN username and password.

As for your problem.. I can't really say. I tested his script with PIA and it seemed fine (granted I don't use it now).

dregus · 26. März 2021

Zitat von KM0201

OP I removed your personal info from your docker-compose, but I'd agree w/ the above... not sure how many have seen it so you need to change your VPN username and password.

As for your problem.. I can't really say. I tested his script with PIA and it seemed fine (granted I don't use it now).

Thanks for being cautious, but that wasn't my user and pass. It was a lazy attempt to put something there. Also, when I use the 2.1 version I'm no longer able to edit the stack on the stack menu. I have to remove all the containers then redeploy.

Soma · 26. März 2021

@OP

Didn't watch or know the video but, by looking at the compose, some things imediatly, shows wrong configuration ot the stack:

On radarr:

Zitat von dregus

- UMASK_SET to UMASK #optional

This will give you errors. Proper environment variable is set this way:

linuxserver/radarr - LinuxServer.io

Although, on new images, it's deprecated:

Deprecate UMASK_SET in favor of UMASK in baseimage · linuxserver/docker-radarr@30ed04d · GitHub

Also, haugene/transmission.... use's docker-compose v3.3 (although, I don't know if this is problematic).

Maybe it's better to use the same version.

These are just some errors that pop up.

Go to each github of each service and try to understand where your errors are.

dregus · 26. März 2021

Zitat von Soma

Also, haugene/transmission.... use's docker-compose v3.3 (although, I don't know if this is problematic).
Maybe it's better to use the same version.

I'm using portainer to install this as a Stack. That being said, if I use anything other than 'version 2.1', my edit privileges are revoked because "This stack was made outside of Portainer"

dregus · 28. März 2021

Figured it out. Needed to use 'haugene/transmission-openvpn:3.3' and everything worked fine. I found the solution on this thread

Easy Automated Home Media Server errors

Jetzt mitmachen!

Ähnliche Themen

Stack Deployment error 'yaml: unmarshal errors: