Posts by aptalca

Two official options here: Emby for Kodi - Emby

One syncs with the internal database, the other lets you access your emby content through a plugin

For play state syncing, I use trakt.tv

Quote from sonic00

Thank you for the hint. That did the trick - had to google a bit, how to mount a nsf shared folder, but I got it to worked now. Great Addon

Another quick hint, all the apps in our docker addons run as the user nobody (id 65534) and group user (99) because running as root is not recommended for many of them. So make sure that the mount points have permissions that allow access to that user

Another option would be to not define any restart options for the container and use a systemd service to manage it

Quote from sonic00

Hey there,

I just installed Plex via the LE docker repo. I have access to the server and it looks like its running so far.

But I can't add any share media folders from my NAS. I tried to Map the NSF Share in the settings, as you described, but when I do this I can't access Plex anymore (it just wont't start). I disabled and enabled the Addon, restarted Kodi (using Libreelec 8.2.5. with RP2), but nothing helps. If i chance the mapping back to the standard "/storage/tvshows" (for example) Plex is starting again.

The NSF share is working fine, since I am using it for my Kodi library. I also tried SMB share but with the same issue.

May I miss something!?

edit:

Some more information. When I edit the settings file to map to my shared network folder, it looks like the whole image isn't even recognized by Docker.

I tried to use the commnd "docker ps -a" to to see all images, but its completley blank. When I reset the settings to default the image show perfectly and Plex is starting.

I don't think I did anything wrong with the mapping since I am using the tree folder structure inside Kodi to point to the right direction. So I can't see why Docker can't recognize the image after I changed the settings?

Here is my changed setting file:

Code

<settings>
    <setting id="E_VERSION" value="public" />
    <setting id="V_config" value="/storage/.kodi/userdata/addon_data/docker.linuxserver.plex" />
    <setting id="V_data_movies" value="nfs://192.168.178.100/Media/Movies/" />
    <setting id="V_data_tvshows" value="/storage/tvshows" />
    <setting id="V_transcode" value="/storage/downloads/plextemp" />
</settings>

Display More

You can't use an nfs:// address as a location map, docker does not recognize that. You need to mount the nfs share in libreelec to a local path, and use that local path in addon settings

Glad to hear it installed.

The avahi errors are harmless, it's because libreelec/coreelec already has avahi running and the one in the container complains, but the addon turns it off shortly after the container starts.

I'm not sure what that framework error is, the line is cut off and I can't see. Hopefully that's also harmless.

With regards to volume mappings, pay attention to the addon settings. There, you are mapping the container folders /data/movies and /data/tvshows to folders on the host. By default they are /storage/videos and /storage/tvshows. So if you place a file in /storage/videos on coreelec, inside the container (or in plex settings) it will show up under /data/movies.

Quote from Martynet

here

Yup, that's exactly the issue. I'll try and fix that at some point, but in all honesty, my priority is always libreelec. We don't officially support coreelec. Also none of our team members at linuxserver run coreelec so we can't easily test that either.

In the short term, you can modify the following file and replace LIBREELEC_ARCH with COREELEC_ARCH and disable and reenable the addon and it should work (don't uninstall)

/storage/.kodi/addons/docker.linuxserver.plex/bin/docker.linuxserver.plex

keep in mind that if you ever uninstall and reinstall the addon, you'll have to edit that file again

Hmm the error is docker reference format, which suggests that there is an issue with one of the parameters. Did you change any of the addon settings? If so, go back to default and try again.

If not, it could be an issue with coreelec. I suspect the way I determine the arch is no longer working. They probably renamed it.

Here's my logic to determine whether it's x86_64 or arm: "sed -e '/LIBREELEC_ARCH/ !d' -e 's/[^.]*\.\([^"]*\).*/\1/' /etc/os-release"

If they renamed it to COREELEC_ARCH that would surely break it.

Can you do "cat /etc/os-release" and post the output?

Thanks

Quote from Martynet

I managed to download Plex image manually and run it through commands. Does this help? See attached.

But still nothing under: 192.168.1.50:32400/web/

That doesn't help. Please delete all instances of plex and reinstall the linuxserver addon. And then get the systemd logs

Quote from Martynet

The other commands need a container name, which I don't have. I posted log earlier. Unless you mean a different log?

The service/container name is "docker.linuxserver.plex"

"systemctl status docker.linuxserver.plex.service" will tell you the current status of the systemd service that is responsible for creating and starting the container

"journalctl -u docker.linuxserver.plex.service" will show you the log

Since you mentioned there is no running container on your system when the addon is enabled, there must have been an error with systemd. We need to see the log to troubleshoot that.

I just installed the addon on a fresh test instance and it fired right up

Don't stop at two, try the other ones too. Without the log I can't help you

Please read the forum thread I mentioned earlier. It tells you how to troubleshoot and get docker logs

Quote from Martynet

I installed LinuxServer.io add-on Repo. And then I installed docker add-on and Plex Media Server. Which I can't access through a web browser, because I was told that I have to forward a port between Docker and PMS, otherwise I won't be able to access it...

Anyway, if there's any easier way to install PMS, I'm all ears

Thank you

Don't know who told you that but that's inaccurate.

Post a log or I can't help you

See instructions in the pinned post about the docker addons in addon support

Quote from Martynet

I installed PMS through Docker and apparently, the port Plex is listening to has to be forwarded. Because when I try to access PMS through http://192.168.1.xx:32400/web it won't open.

Did you install through the linuxserver docker addon or in docker yourself through command line or portainer?

The addon has plex run in host mode, so all ports should be exposed on the host automatically.

How did you conclude the port has to be forwarded?

Did you check the logs? Is plex running?

Quote from Martynet

Hey guys, I just installed plex server but can't access it through the Web browser until I forward the right port. Can anyone help me with that please?

Thank you very much

Which one did you install? What do you mean by "forward the right port"?

Need more info on what you did

Quote from menix

Hi,

Please can you post a tutorial or a link on how to get Letsencrypt working with NextClous https certificate?

Thank you,

Best regards,

Navigate to your letsencrypt addon config folder. Under nginx/proxy-confs you'll see two nextcloud confs, one for subdomain, and another for subfolder.

Pick one, follow the instructions at the top of the file to make the necessary changes to your nextcloud config, and then rename that proxy conf file to remove sample at the end (so it becomes blah.conf).

When you reboot, you should be able to access nextcloud through your domain and either subdomain and subfolder.

The full instructions for reverse proxy are linked from the letsencrypt image description at GitHub - linuxserver/docker-letsencrypt

Keep in mind that the libreelec docker addons by lsio already run in the same user defined bridge network so you don't have to change that.

Quote from RonnieStark

Hello,

I'm a bit new with the dockers, so I figured out myself that using Portainer would help me to add new services into my beloved raspberry pi 3 kodi.

I installed docker and portainer from the Add ons menu , opened a webpage from the correct port, I finally setted up my portainer, all went well. I decided to give a first try by following a tutorial, this one : LinuxServer.io docker addons and general docker info , from the Portainer section. I tried to follow the instruction to install LinuxServer’s Calibre OPDS Php Server, but unfortunately my container didn't want to start. By looking to the log it shows the same error all the time :

Code

standard_init_linux.go:178: exec user process caused "exec format error"

But I don't understand how a format error sliped into an auto container manager.

Here is the config of the container.

Thank you for helping me !

Display More

That's the x86_64 image. You need to use the arm version: https://www.linuxserver.io/our-images

If you're new to docker, don't bother with building. Pull already built images from the hub. Stick to images with good documentation, and ones that list the source repo.

Check out the stickied post about docker on le in the addons section of this forum.

Check out https://linuxserver.io/our-images for a bunch of images with good docs (I'm part of that team)

If you have any questions about those images, you can join the discord channel listed on that website

Mariadb is listening on 3306.

The issue is something else that is listening on 8099