Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] feederbox826/stash-s6 - Alternative stash container

Featured Replies

  • 2 months later...

Thank for this, would I have to start from scratch on this if I already have all my metadata and database setup in a previous instance? 

  • Author
9 hours ago, NGMK said:

Thank for this, would I have to start from scratch on this if I already have all my metadata and database setup in a previous instance? 

Nope! There is a compatibility mode for running hotio/stash or stashapp/stash and migration scripts should you choose to move over. It's deailed here in the README

  • 1 month later...

Thanks for this container. I've gotten it installed, and live transcoding is hitting my intel ARC card as desired.

But generating content isn't. I have a lot of high resolution VR content that kills my CPU when it goes to generate previews, covers, etc. Is there something I'm missing to cause generation to also happen on the GPU?

  • Author

Nope, hwaceel is not used for generation and from a community member's tests to force it, yields little to no difference in speeds and instead adds complications.

  • 1 month later...
  • Author
On 2/10/2025 at 4:38 PM, ClarkKrypton said:

Thanks for this container. I've gotten it installed, and live transcoding is hitting my intel ARC card as desired.

But generating content isn't. I have a lot of high resolution VR content that kills my CPU when it goes to generate previews, covers, etc. Is there something I'm missing to cause generation to also happen on the GPU?

On 2/10/2025 at 9:54 PM, feederbox826 said:

Nope, hwaceel is not used for generation and from a community member's tests to force it, yields little to no difference in speeds and instead adds complications.


There has actually been an update for this, but is still only a theory

https://github.com/stashapp/stash/issues/5731

HWAccel has been proven to have significant improvement in speed but will be probably quite a while before it's properly implemented and off the ground in a meaningful capacity

  • 1 month later...
  • 3 weeks later...
On 4/26/2025 at 12:44 AM, wystewart said:

not quite clear to me how to enable hwaccel for an Intel CPU. I read this  https://github.com/feederbox826/stash-s6/blob/main/docs/switch-to-hwaccel.md, but my understanding is that unraid doesn't use dock compose to edit the configuration that way.

 

Would appreciate some guidance.

Think I figured it out.  In docker container settings change repository, add ":hwaccel"

 

Repository: ghcr.io/feederbox826/stash-s6:hwaccel

 

it will automatically then upgrade.

 

Then container settings add a device, /dev/dri

 

I can see in the logs the hwaccel is detected.  Didn't test any video yet.

Edited by wystewart

  • 3 months later...

Hello,

I am using the :hwaccel container. but upon starting the container, it's said it can't build srsly because it doesn't have g++ installed. How can I fix this?
I am on Unraid 6.12.15. Should i upgrade to UnRaid 7.x?


× Failed to build `srsly==1.0.7`
├─ The build backend returned an error
╰─ Call to `setuptools.build_meta.build_wheel` failed (exit status: 1)

[stderr]

/pip-install/cache/builds-v0/.tmpDUmOjP/lib/python3.13/site-packages/setuptools/dist.py:759:

SetuptoolsDeprecationWarning: License classifiers are deprecated.

!!

********************************************************************************

Please consider removing the following classifiers in favor of a

SPDX license expression:

License :: OSI Approved :: MIT License

See

https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license

for details.

********************************************************************************

!!

self._finalize_license_expression()

error: command 'g++' failed: No such file or directory

hint: This usually indicates a problem with the package or the build

environment.

help: srsly (v1.0.7) was included because spacy (v2.3.9) depends on

srsly

Starting stash...

  • Author

Wow, unraid really didn't like me trying to reply.

g++ and dependencies are kind of a hard edge case to account for, so I've limited dependencies to what CommunityScripts has. for your case, I can't seem to find the other dependencies but this should cover it. Enter the container shell and execute the following command running as root

on :alpine and :hwaccel-alpine
```sh
apk add build-base python3-dev
```
on :hwaccel

apt install build-essential

14 hours ago, Griffon Ace said:

Hello,

I am using the :hwaccel container. but upon starting the container, it's said it can't build srsly because it doesn't have g++ installed. How can I fix this?
I am on Unraid 6.12.15. Should i upgrade to UnRaid 7.x?


× Failed to build `srsly==1.0.7`
├─ The build backend returned an error
╰─ Call to `setuptools.build_meta.build_wheel` failed (exit status: 1)

[stderr]

/pip-install/cache/builds-v0/.tmpDUmOjP/lib/python3.13/site-packages/setuptools/dist.py:759:

SetuptoolsDeprecationWarning: License classifiers are deprecated.

!!

********************************************************************************

Please consider removing the following classifiers in favor of a

SPDX license expression:

License :: OSI Approved :: MIT License

See

https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license

for details.

********************************************************************************

!!

self._finalize_license_expression()

error: command 'g++' failed: No such file or directory

hint: This usually indicates a problem with the package or the build

environment.

help: srsly (v1.0.7) was included because spacy (v2.3.9) depends on

srsly

Starting stash...

Thank you. I have tried

apt install build-essential

I have to apt get update first, and then it installs fine.
however, i still have errors building srsly.
But stash is working fine as far as i am concerned. So i'm not really sure what these SRSLY and SPACY are used for.

Here is the full error logs.

INFO[2025-09-11 10:06:23] 🐍 Installing/upgrading python requirements...
× Failed to build `srsly==1.0.7`
├─ The build backend returned an error
╰─ Call to `setuptools.build_meta.build_wheel` failed (exit status: 1)

[stdout]
running bdist_wheel
running build
running build_py
copying srsly/__init__.py -> build/lib.linux-x86_64-cpython-313/srsly
copying srsly/_json_api.py -> build/lib.linux-x86_64-cpython-313/srsly
copying srsly/_msgpack_api.py -> build/lib.linux-x86_64-cpython-313/srsly
copying srsly/_pickle_api.py -> build/lib.linux-x86_64-cpython-313/srsly
copying srsly/about.py -> build/lib.linux-x86_64-cpython-313/srsly
copying srsly/util.py -> build/lib.linux-x86_64-cpython-313/srsly
copying srsly/cloudpickle/__init__.py ->
build/lib.linux-x86_64-cpython-313/srsly/cloudpickle
copying srsly/cloudpickle/cloudpickle.py ->
build/lib.linux-x86_64-cpython-313/srsly/cloudpickle
copying srsly/cloudpickle/cloudpickle_fast.py ->
build/lib.linux-x86_64-cpython-313/srsly/cloudpickle
copying srsly/cloudpickle/compat.py ->
build/lib.linux-x86_64-cpython-313/srsly/cloudpickle
copying srsly/msgpack/__init__.py ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/_ext_type.py ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/_msgpack_numpy.py ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/_version.py ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/exceptions.py ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/util.py ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/tests/__init__.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests
copying srsly/tests/test_json_api.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests
copying srsly/tests/test_msgpack_api.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests
copying srsly/tests/test_pickle_api.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests
copying srsly/ujson/__init__.py ->
build/lib.linux-x86_64-cpython-313/srsly/ujson
copying srsly/tests/cloudpickle/__init__.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/cloudpickle
copying srsly/tests/cloudpickle/cloudpickle_file_test.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/cloudpickle
copying srsly/tests/cloudpickle/cloudpickle_test.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/cloudpickle
copying srsly/tests/cloudpickle/testutils.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/cloudpickle
copying srsly/tests/msgpack/__init__.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_buffer.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_case.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_except.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_extension.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_format.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_limits.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_memoryview.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_newspec.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_numpy.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_pack.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_read_size.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_seq.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_sequnpack.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_stricttype.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_subtype.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/msgpack/test_unpack.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/msgpack
copying srsly/tests/ujson/__init__.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/ujson
copying srsly/tests/ujson/test_ujson.py ->
build/lib.linux-x86_64-cpython-313/srsly/tests/ujson
copying srsly/msgpack/_packer.pyx ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/_unpacker.pyx ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/buff_converter.h ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/pack.h ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/pack_template.h ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/sysdep.h ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/unpack.h ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/unpack_define.h ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/msgpack/unpack_template.h ->
build/lib.linux-x86_64-cpython-313/srsly/msgpack
copying srsly/ujson/JSONtoObj.c ->
build/lib.linux-x86_64-cpython-313/srsly/ujson
copying srsly/ujson/objToJSON.c ->
build/lib.linux-x86_64-cpython-313/srsly/ujson
copying srsly/ujson/ujson.c ->
build/lib.linux-x86_64-cpython-313/srsly/ujson
copying srsly/ujson/py_defines.h ->
build/lib.linux-x86_64-cpython-313/srsly/ujson
copying srsly/ujson/version.h ->
build/lib.linux-x86_64-cpython-313/srsly/ujson
copying srsly/tests/ujson/334-reproducer.json ->
build/lib.linux-x86_64-cpython-313/srsly/tests/ujson
copying srsly/tests/ujson/sample.json ->
build/lib.linux-x86_64-cpython-313/srsly/tests/ujson
running build_ext
building 'srsly.msgpack._unpacker' extension
g++ -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -fPIC
-D__LITTLE_ENDIAN__=1 -Isrsly/msgpack -I/usr/local/include/python3.13 -I.
-I/pip-install/cache/sdists-v9/pypi/srsly/1.0.7/oVH25yt5PVUYW1SNMZZaN/src/include
-I/pip-install/cache/builds-v0/.tmpjdIJpE/include
-I/usr/local/include/python3.13 -c srsly/msgpack/_unpacker.cpp -o
build/temp.linux-x86_64-cpython-313/srsly/msgpack/_unpacker.o -O2
-Wno-strict-prototypes -Wno-unused-function

[stderr]
/pip-install/cache/builds-v0/.tmpjdIJpE/lib/python3.13/site-packages/setuptools/dist.py:759:
SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!


********************************************************************************
Please consider removing the following classifiers in favor of a
SPDX license expression:

License :: OSI Approved :: MIT License

See
https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license
for details.

********************************************************************************

!!
self._finalize_license_expression()
cc1plus: warning: command-line option ‘-Wno-strict-prototypes’ is valid
for C/ObjC but not for C++
srsly/msgpack/_unpacker.cpp:878:72: warning: ‘Py_UNICODE’ is deprecated
[-Wdeprecated-declarations]
878 | static CYTHON_INLINE size_t __Pyx_Py_UNICODE_strlen(const
Py_UNICODE *u) {
|
^
In file included from /usr/local/include/python3.13/unicodeobject.h:1014,
from /usr/local/include/python3.13/Python.h:80,
from srsly/msgpack/_unpacker.cpp:36:
/usr/local/include/python3.13/cpython/unicodeobject.h:10:37: note:
declared here
10 | Py_DEPRECATED(3.13) typedef wchar_t Py_UNICODE;
| ^~~~~~~~~~
srsly/msgpack/_unpacker.cpp: In function ‘size_t
__Pyx_Py_UNICODE_strlen(const Py_UNICODE*)’:
srsly/msgpack/_unpacker.cpp:879:23: warning: ‘Py_UNICODE’ is deprecated
[-Wdeprecated-declarations]
879 | const Py_UNICODE *u_end = u;
| ^~~~~
/usr/local/include/python3.13/cpython/unicodeobject.h:10:37: note:
declared here
10 | Py_DEPRECATED(3.13) typedef wchar_t Py_UNICODE;
| ^~~~~~~~~~
srsly/msgpack/_unpacker.cpp: In function ‘int
__pyx_f_5srsly_7msgpack_9_unpacker_get_data_from_buffer(PyObject*,
Py_buffer*, char**, Py_ssize_t*, int*)’:
srsly/msgpack/_unpacker.cpp:2605:17: error: ‘PyObject_AsReadBuffer’ was
not declared in this scope; did you mean ‘PyObject_GetBuffer’?
2605 | __pyx_t_2 = PyObject_AsReadBuffer(__pyx_v_obj, ((void
const **)__pyx_v_buf), __pyx_v_buffer_len); if (unlikely(__pyx_t_2 ==
((int)-1))) __PYX_ERR(0, 136, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~~~~
| PyObject_GetBuffer
srsly/msgpack/_unpacker.cpp: In function ‘long int
__Pyx_PyInt_As_long(PyObject*)’:
srsly/msgpack/_unpacker.cpp:9634:46: error: too few arguments to
function ‘int _PyLong_AsByteArray(PyLongObject*, unsigned char*, size_t,
int, int, int)’
9634 | int ret = _PyLong_AsByteArray((PyLongObject *)v,
| ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
9635 | bytes,
sizeof(val),
| ~~~~~~~~~~~~~~~~~~~
9636 | is_little,
!is_unsigned);
|
~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.13/longobject.h:107,
from /usr/local/include/python3.13/Python.h:82:
/usr/local/include/python3.13/cpython/longobject.h:111:17: note:
declared here
111 | PyAPI_FUNC(int) _PyLong_AsByteArray(PyLongObject* v,
| ^~~~~~~~~~~~~~~~~~~
srsly/msgpack/_unpacker.cpp: In function ‘int
__Pyx_PyInt_As_int(PyObject*)’:
srsly/msgpack/_unpacker.cpp:9830:46: error: too few arguments to
function ‘int _PyLong_AsByteArray(PyLongObject*, unsigned char*, size_t,
int, int, int)’
9830 | int ret = _PyLong_AsByteArray((PyLongObject *)v,
| ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
9831 | bytes,
sizeof(val),
| ~~~~~~~~~~~~~~~~~~~
9832 | is_little,
!is_unsigned);
|
~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/python3.13/cpython/longobject.h:111:17: note:
declared here
111 | PyAPI_FUNC(int) _PyLong_AsByteArray(PyLongObject* v,
| ^~~~~~~~~~~~~~~~~~~
error: command '/usr/bin/g++' failed with exit code 1

hint: This usually indicates a problem with the package or the build
environment.
help: `srsly` (v1.0.7) was included because `spacy` (v2.3.9) depends on
`srsly`

Starting stash...
───────────────────────────────────────

INFO[2025-09-11 10:06:29] using config file: /config/config.yml
INFO[2025-09-11 10:06:32] [InitHWSupport] Supported HW codecs [2]:
H264 NVENC HQ profile - h264_nvenc
H264 NVENC - h264_nvenc
INFO[2025-09-11 10:06:32] stash version: v0.28.1 (cc6917f2) - Official Build - 2025-03-19 23:01:38
INFO[2025-09-11 10:06:32] stash is listening on 0.0.0.0:9999
INFO[2025-09-11 10:06:32] stash is running at http://localhost:9999/
ERRO[2025-09-11 10:06:35] Couldn't retrieve latest version: Github API request failed: Get "https://api.github.com/repos/stashapp/stash/releases/latest": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

  • Author

Sorry, that's into the realm of srsly why it isn't compiling properly, if I had to guess it looks like it could be a python version they don't support.
srsly and spacy arent used in any of the plugins at stashapp/CommunityScripts so it could be from another plugin index you added?

On 9/12/2025 at 5:09 AM, feederbox826 said:

Sorry, that's into the realm of srsly why it isn't compiling properly, if I had to guess it looks like it could be a python version they don't support.
srsly and spacy arent used in any of the plugins at stashapp/CommunityScripts so it could be from another plugin index you added?


Thank you for putting me on the right direction. You are right. I managed to resolve the problem.

  • uninstall all the plugins and metadata providers

  • browse the plugins directory and delete all folders that I don't recognize as standard plugins

  • delete the 'requirements.txt' found in plugin directory and also another 'requirements.txt' in the main config folder (in my case it's in /mnt/user/appdata/stash-s6)

  • Restart the docker container and let it rebuild the 'requirements.tx'

The container starts without error. Now i'll work on reinstalling the plugins and scrapers one-by-one. Hopefully i can isolate the problematic plugins along the way.

  • Author

if you restart the container after removing requirements.txt it should populate it with a comment on which file it's from above it

```
# /plugins/plugin/requirements.txt

spacy
```

Thanks for your work here - finally getting some hardware transcoding going on my stash instance.

Transcoding actually seems to be going quite smoothly. The only thing I'm running into in logs:

[transcode] ffmpeg error when running command </usr/bin/ffmpeg -hide_banner -v error -hwaccel qsv -hwaccel_output_format qsv -i /whisparr/VIDEOFILE.mp4 -c:v h264_qsv -global_quality 20 -preset faster -movflags frag_keyframe+empty_moov -vf scale_qsv=format=nv12 -ac 2 -f mp4 pipe:>: libva info: VA-API version 1.22.0 libva info: User environment variable requested driver '' libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/_drv_video.so libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/_drv_video.so libva info: Trying to open /usr/lib/dri/_drv_video.so libva info: Trying to open /usr/local/lib/dri/_drv_video.so libva info: va_openDriver() returns -1

Any idea what this error might be triggered by?

  • Author
2 minutes ago, wiffle said:

Thanks for your work here - finally getting some hardware transcoding going on my stash instance.

Transcoding actually seems to be going quite smoothly. The only thing I'm running into in logs:

[transcode] ffmpeg error when running command </usr/bin/ffmpeg -hide_banner -v error -hwaccel qsv -hwaccel_output_format qsv -i /whisparr/VIDEOFILE.mp4 -c:v h264_qsv -global_quality 20 -preset faster -movflags frag_keyframe+empty_moov -vf scale_qsv=format=nv12 -ac 2 -f mp4 pipe:>: libva info: VA-API version 1.22.0 libva info: User environment variable requested driver '' libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/_drv_video.so libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/_drv_video.so libva info: Trying to open /usr/lib/dri/_drv_video.so libva info: Trying to open /usr/local/lib/dri/_drv_video.so libva info: va_openDriver() returns -1

Any idea what this error might be triggered by?


Try some of the steps in https://github.com/feederbox826/stash-s6/blob/main/docs/arc-troubleshooting.md

but if transcoding is still working, it's probably safe to ignore

1 minute ago, feederbox826 said:


Try some of the steps in https://github.com/feederbox826/stash-s6/blob/main/docs/arc-troubleshooting.md

but if transcoding is still working, it's probably safe to ignore

thanks. is this specific to the stash container or is this an overall install on the host ie. unraid server altogether?

i'm not too familiar with the apt install command.

Also - the above was when tryign to run a separate stash-s6 instance.

This is the error I get when changing the base 2025-09-14 16:54

Error [transcode] ffmpeg error when running command </usr/bin/ffmpeg -hide_banner -v error -hwaccel qsv -hwaccel_output_format qsv -i VIDEOFILE.mp4 -c:v h264_qsv -global_quality 20 -preset faster -movflags frag_keyframe+empty_moov -vf scale_qsv=format=nv12 -ac 2 -f mp4 pipe:>: libva info: VA-API version 1.22.0

libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so

libva info: Found init function __vaDriverInit_1_22

libva info: va_openDriver() returns 0

libva info: VA-API version 1.22.0

libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so

libva info: Found init function __vaDriverInit_1_22

libva info: va_openDriver() returns 0

Seems like a different error. Transcoding still seems to work.

Edited by wiffle

  • 2 months later...

Hi,

I have the container installed and it works but i can't seem to enable hardware accel

I set it up with the device added to the container: SsMlaBv.png (1191×849)

but i get this message in the logs at boot up of the container: F79oawF.png (899×327)

I know it should work because i have plex installed and it seems to work fine: Mq3AZkr.png (703×458)

Can you please advise?

  • Author

Can you post the startup logs for stash-s6? this is also available via stash-s6 helper with "get logs" or at /config/stash-s6.log

11 minutes ago, feederbox826 said:

Can you post the startup logs for stash-s6? this is also available via stash-s6 helper with "get logs" or at /config/stash-s6.log

image.png

  • Author

There you go, delete ffmpeg/ffprobe at /config, it's the version downloaded by stash which is missing hwaccel support

Hmm that didnt work, I just restarted:

Logs:
image.png

I then see this in the app log

image.png

And this is the cpu load when opening a video

image.png

  • Author

can you pull the container startup logs? not from within stash but from the terminal, not everything is in the logfile yet

Like this?

image.png

WARN[2025-11-19 09:14:55]  /config/plugins not found, skipping requirement search
WARN[2025-11-19 09:14:55]  /config/scrapers not found, skipping requirement search
euv: attempting to install with uv-pip 0.2
duv: Running uv pip install from requirements file with target /pip-install/install
Using CPython 3.12.12 interpreter at: /usr/bin/python
Audited 9 packages in 28ms
INFO[2025-11-19 09:14:55] using config file: /config/config.yml 
INFO[2025-11-19 09:14:56] [InitHWSupport] Supported HW codecs [0]: 
INFO[2025-11-19 09:14:56] stash version: v0.29.3 (7716c4dd) - Official Build - 2025-11-06 06:09:06 
INFO[2025-11-19 09:14:56] stash is listening on 0.0.0.0:9999 
INFO[2025-11-19 09:14:56] stash is running at http://localhost:9999/ 
INFO[2025-11-19 09:14:56] Version v0.29.3 (7716c4dd) is already the latest released 
usermod: no changes
───────────────────────────────────────
XXXXXXXXX 
XXXXXXXXXXXXXXX 
XXXXXXXXX XXXXXXXXX 
XXXXXXXXX XXXXXXXX 
XXXXXXXXXXXXX XXXXXXXXXXXX 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 
XXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXX 
XXXXXXXX XXXXXXXX 
XX X X XX 
XXXXXX X X XXXXX 
XXXXXXXX XX XX XXXXXXXX 
XXXXXXXXXXX XXXXXXXXXXX 
XXXXXXXXX XXXXXXXXX 
XXXXXX XXXXXX 

feederbox826/stash-s6 ++ 
hwaccel-alpine - 2025-11-11 (66da8fe)
───────────────────────────────────────

To support development visit:
https://opencollective.com/stashapp

───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 911
User GID: 911
HW Accel: Jellyfin-ffmpeg

───────────────────────────────────────
entrypoint.sh


INFO[2025-11-19 09:14:55]  Running as 911:911 from PUID/PGID
INFO[2025-11-19 09:14:55]  Additional GID from AVGID: 22
INFO[2025-11-19 09:14:55]  checking common directory permissions
INFO[2025-11-19 09:14:55]  common directories are accessible
INFO[2025-11-19 09:14:55]  fixing permissions on /config/requirements.txt
INFO[2025-11-19 09:14:55]  Installing/upgrading python requirements...

Starting stash...
───────────────────────────────────────

I also get these

2025-11-19T09:13:37.977722083Z INF Response: 304 Redirect httpRequest={"proto":"HTTP/1.1","remoteIP":"remoteip:50713","requestID":"fb18493bd2e6/0ONR2O52Lv-000008","requestMethod":"GET","requestPath":"/customlocales","requestURL":"http://address:9999/customlocales"} httpResponse={"bytes":0,"elapsed":0.020863,"status":304} service=stash

  • Author

Hm everything looks correct, try removing the Jellyfin Driver selector and Driver Selector variables in the config

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.