3 install issues

[dmurphynj]

Describe the issue
Installing on Ubuntu 25.10 so I can take (easy) advantage of the QuickSync technology in my Beelink N150-based mini PC, and ran into a few install issues. Here are the easy solutions.

To Reproduce
Steps to reproduce the issue:

1. Try to do a single-server install using the install.sh script on Ubuntu 25.10.
2. Install fails in several ways:
3. Package install failure - libxmlsec1-openssl
4. uwsgi fails to compile
5. Installing jellyfin-ffmpeg fails (not part of the MediaCMS install, but a post-install item.)

Environment (please complete the following information):

• OS: Ubuntu 25.10
• Installation method: Single server

Additional context
Changes in Ubuntu 25.10 (and, presumably, 26.04 coming up) made some packaging changes that affect MediaCMS.

1. package name needs to change from "libxmlsec1-openssl" to "libxmlsec1-openssl1"
2. Additional compiler flag needed for uwsgi

These can be fixed with:

cd /home/mediacms.io
sed -i 's/<libxmlsec1-openssl>/libxmlsec1-openssl1/g' mediacms/install.sh
sed -i 's/^pip install --no-binary lxml,xmlsec -r requirements.txt$/CFLAGS="-Wno-error=incompatible-pointer-types" &/' mediacms/install.sh

Now, to use the Jellyfin-based ffmpeg with MediaCMS ... It's not supported on Ubuntu 25.10 (they only support LTS, which I understand.)

So I wrote a shell wrapper around a Docker containerized version of ffmpeg. I copied this to /usr/local/bin/ffmpeg-mediacms.sh, and then set FFMPEG_COMMAND in /home/mediacms.io/mediacms/cms/local_settings.py to that.

Kinda nifty. Lets me pass through the VAAPI device to the container, run the proper version of ffmpeg, and not worry about libraries or incompatibilities.

Getting VAAPI working on the host is an exercise left to the reader. (I did it in a Proxmox VM on this little Beelink.)

Just a few items I wanted to share as Ubuntu 26.04 comes up, these seem to be changes we're going to need.

** EDITED TO ADD **:
I suppose it would help if I attached a corrected version of the ffmpeg-mediacms.sh script.

1. Ensure to add www-data to the docker group (usermod -aG docker www-data) on the host
2. Updated script to add render permissions to the container (so it can access /dev/dri/renderD128)
3. Be sure to fully restart mediacms - including the nginx and uwsgi processes - after installing so they can pickup the right permissions.

Also attached an updated files/helpers.py file that changes the h264/h265/vp9 render encodings to vaapi-enabled ones. No guarantees about lack of bugs; I'm not a programmer by trade....

ffmpeg-mediacms.sh
helpers.py

[dmurphynj]

I need to do more homework to determine if libxmlsec1-openssl1 or libxmlsec1-openssl3 is the correct choice. I used openssl1 and everything appears to be working fine but would certainly be better if we could use openssl3. I just haven’t tried it yet.

[mrjoshuap]

This is likely due to Python 3.13 and loosely affiliated with #1467