assassin6

joined 4 months ago
sorted by: new top controversial old
Network problems with Plex in docker in c/docker@programming.dev
[–] assassin6@lemmy.dbzer0.com 1 points 2 months ago

Yes, I'm using hub.docker.com and portainer. The other 7 or so containers are in bridge mode on the network I set up. Plex, per the linuxserver.io docs, needs to be under network mode host.

I have set port forwarding on my router to allow external access to port 32400.

5
Network problems with Plex in docker (lemmy.dbzer0.com)
 

I am hoping that you awesome people can help me with something I've noticed in my Plex logs. Quick notes on my set up:

Mini PC running Ubuntu 22.04, portainer, Plex, arrs and calibre all running in docker. All of these except Plex are using a bridge network that I created in portainer. The PC is connected to the router by ethernet cable, and I have set up a static IP in the router settings. I have also added the static IP info into the network settings in Ubuntu.

The following text is repeated over and over in the Plex Media Server log, about 6 seconds apart. My playback is mostly fine, but I have been experiencing buffering. Regardless this can't be right!.

n.b. I did post elsewhere but I feel that this is not necessarily Plex related and you can likely help with this more technical question.

DEBUG - NetworkInterface: received Netlink message len=88, type=RTM_DELADDR, flags=0x0 Aug 22, 2024 18:51:49.636 [139016208919352] DEBUG - NetworkInterface: Netlink address message family=2, index=3, flags=0x0 Aug 22, 2024 18:51:49.636 [139016208919352] DEBUG - Network change. Aug 22, 2024 18:51:49.636 [139016208919352] DEBUG - NetworkInterface: Notified of network changed (force=0) Aug 22, 2024 18:51:49.637 [139016208919352] DEBUG - Network change notification but nothing changed.

calibre integration with readarr problems in docker in c/docker@programming.dev
[–] assassin6@lemmy.dbzer0.com 2 points 2 months ago (1 children)

You were correct, thank you so much. The apps were in the default network docker0. I looked into it, and the easiest option for my situation was simply to create another bridge network and move my apps into that. Now readarr can find Host = Calibre.

5
calibre integration with readarr problems in docker (lemmy.dbzer0.com)
 

I have readarr and all other arrs working in Ubuntu with docker portainer. I followed the trash guides and LinuxServerio guides to get me this far. I want to expand my book library, and so I have added calibre.

After having calibre import my book library, I went to readarr to delete the root, and re-add it with the new path to the calibre library. I am having problems with the Calibre Settings on the Add Root page.

The calibre server is listening at 172.18.0.2, port 8081, HTTP. I have created a user account on the calibre "sharing over the net" page. In readarr, I have set the Calibre Host to 172.18.0.2 and the Calibre Port to 8081. When I click save, I get the error Unknown exception: Http request timed out.

Most of the guides I have found are 3 or 4 years old. On one guide the Calibre Host was set to: calibre. That doesn't work. Setting the Host to the IP of my server doesn't work either.

Can any one help? I don't know if I have a permissions or firewall problem, or if I am just doing something wrong. The calibre logs are not showing any issues. I have copied the .yaml files used below.

-services:

  • calibre:
  • image: lscr.io/linuxserver/calibre:latest
  • container_name: calibre
  • security_opt:
    • seccomp:unconfined
  • environment:
    • PUID=1000
    • PGID=1000
    • TZ=Europe/London
    • CLI_ARGS = #optional
  • volumes:
    • /data/calibre:/config
    • /data/Media/calibre:/library
    • /data/Media/books:/upload
  • ports:
    • 8080:8080
    • 8081:8081
  • restart: unless-stopped

-services:

  • readarr:
  • image: lscr.io/linuxserver/readarr:develop
  • container_name: readarr
  • environment:
    • PUID=1000
    • PGID=1000
    • TZ=Europe/London
  • volumes:
    • /data/readarr:/config
    • /data/Media/calibre:/library
    • /data/Media/downloads:/downloads
  • ports:
    • 8787:8787
  • restart: unless-stopped
sonarr in docker with seedbox help please - solved in c/docker@programming.dev
[–] assassin6@lemmy.dbzer0.com 1 points 3 months ago* (last edited 3 months ago)

In the log file, verbatim. In sonarr (queue page) it still says seedit4me

sonarr in docker with seedbox help please - solved in c/docker@programming.dev
[–] assassin6@lemmy.dbzer0.com 2 points 3 months ago

For torrents I don't have an incomplete folder. As I'm using a seedbox it doesn't seem necessary.

sonarr in docker with seedbox help please - solved in c/docker@programming.dev
[–] assassin6@lemmy.dbzer0.com 1 points 3 months ago* (last edited 3 months ago) (2 children)

Interesting idea, I've never done this before. I tried opening the console from within the sonarr portainer container. That failed with "unable to retrieve image details"

On searching this, I was able to connect using:

sudo docker exec -it sonaar bash

This put me at the root of the container, and from there, I could navigate through:

root@xx:/data/torrents/rtorrent/Completed/tv-sonarr

From there I could see the file. But the permissions were for user abc and group "users". But I found the same when I browsed to the usenet downloads area, so I think this is more because of the way I logged in to root. I don't have any issues with usenet and sonaar. ID from there shows my uid as 0 and gid 0

sonarr in docker with seedbox help please - solved in c/docker@programming.dev
[–] assassin6@lemmy.dbzer0.com 1 points 3 months ago* (last edited 3 months ago)

I don't think the issue is the volume because sonarr is finding my usenet downloads.

The actual folder structure is /data/usenet/download. sonarr is given the volume mount: /data
It gets the download location from SAB. All works fine.

Equating this to my situation, I am expecting the folder mapping to put the download in the location /data/torrents/rtorrent etc Again this matches the info sonarr receives from rutorrent. And the volume mount /data should be allowing access same as it gets to the usenet folders.

5
sonarr in docker with seedbox help please - solved (lemmy.dbzer0.com)
submitted 3 months ago* (last edited 3 months ago) by assassin6@lemmy.dbzer0.com to c/docker@programming.dev
8 comments fedilink
 

Edit - marking as solved.

  • Remote path: /home/seedit4me
  • local path: /data

This is now working, I don't know why it wasn't before. ‐------------

I have followed the docs and have the recommended folder structures for my Plex and arrs setup.

sonarr has a volume set as /data which gives it access to e.g. /data/usenet/downloads This is working fine with SABnzdb

I am using a seedbox for torrents. Looking at ruTorrent on the seedbox, I can see that the local download folder there is set to: /home/seedit4me/torrents/rtorrent

sonarr is reporting "No files found are eligible for import in:

  • /home/seedit4me/torrents/rtorrent/Completed/tv-sonarr/filename.mkv

I have set a remote path in the download clients page in sonarr as follows:

  • Host - ****.seedit4.me
  • Remote path: /home/seedit4me
  • local path: /data

I have ftp'd the mkv file to actual folder structure:

  • /data/torrents/rtorrent/Completed/tv-sonaar/filename.mkv

The permissions on this file are:

  • -rw-rw-r--

the folder permissions are:

  • drwxrwxr-x 2 myacct myacct 4096 Aug 2 11:41 .
  • drwxrwxr-x 3 myacct myacct

My uid=1000(my acct), same for gid I have set these as the PUID and PGID env variables in sonarr

The log file in sonarr is reporting: |Error|DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr: /home/(removed)/torrents/rtorrent/Completed/tv-sonarr/filename.mkv

Seeing this, i tried mapping /home/(removed)/ to /data/ but that doesn't work either.

Can anyone guide me on what I am doing wrong? I feel like I've checked everything so I can't understand the issue at all.---