saarg

Ffmpeg is installed from the alpine repo, so we can't update until alpine updates it. libxml2 is installed in the container, if that is what's needed.

You can thank ubiquiti for this. They released 6.2.23 and then pulled it. You should never have unifi-controller on auto-update in my opinion.

It's not us that pulls in the wrong ffmpeg. It's a dependency of Jellyfin and gets chosen by the Jellyfin deb as the specific version they want. So you have to ask Jellyfin to fix that.

Did you check the log?

Which instructions are you talking about? Use a stable release instead of an RC release of you have issues.

Our containers are not multi user. Why not set up multiple containers?

It does work. You guys are not posting enough information to find out what is the issue.

You don't need to add any certs in Plex, that is the point with using a reverse proxy.

That is the default path for the log file. The firs hit on Google tells you how you can change the path.

Even if you use cache: yes, the files will be moved to the array. What exactly is it that is written in your /data mount that you mean should go in /config? The more info you provide, the easier it is to help. And also post the docker run command.

Why do you need multiple ports? The container can't handle multiple users, so I don't see the value. If you read aptalcas comment, you can see that you can do this with the customizing option we have in our containers.

It can't. Setup multiple containers if you want more servers.

Has that been reported to us before? The big you linked to is in the snipe-it repo and we don't follow issues there.

It's not in our documentation and I can't remember having it there either.

https://github.com/linuxserver/docker-projectsend/issues/17

3.0.1? That's what we are building, so you should get that. If you want a beta release, then we don't build that.

Yes, the context path was added back to your airsonic template. Remove it and it will work again.

Where did you get the http and https proxy env variables from? That's not something from our container.

You haven't said what the problem is, just that it's similar and you get the error message when you try to connect. You can't access nextxloud? If you remove and install the container you will still have the database as the appdata folder is not deleted when removing a container. If you want to set up a new database using the same settings you did for the current one, just stop mariadb and delete the appdata folder for mariadb and start the container again. That will get you a clean database. If you do this, you will have to set up nextxloud again also as the settings and users are stored in the database. The files are still in /data, so you will still have them, but you need to add the users again and then scan for new files manually.

Please post the docker run command so we can see the full picture.

Sorry, I don't know how to fix that problem. You are inside the mariadb container when executing the command?

Also set the version variable to docker, or else Plex will be updated on the next restart of the container.

If it's not listed under mods in the readme, there are none.

A little late to the party, but you made two users with the same name, only difference was the difference in capital letters. If you look in the picture of your /data folder you can see that all user folders are in small letters, so that will be a problem. As for the issue athat there are no folders in the share you chose for /data when installing it fresh, that sounds like you didn't set the path to /data when you went through the installer. Do you see the folders if you check the directory inside the container?

Then it's probably a corrupt database. How that happened is hard to say. It could be a forced shutdown of the container.