Josh.5

Probably a permission issue on that directory

But you are doing it on your browser

So you are using steam link through a vnc connection? Steam is playing the game and encoding it to a video. Then you have steam link connecting to it locally and decoding that video. Then you have vnc re-encoding that display again... Why would you do this?

How do you start the container with steam link? I know nothing about this. I thought steam link was the app on Android iOS etc....

The issue is that this plugin was never designed to be placed at the end of the plugin stack. It was always intended that other plugins would be run after it. That being said, rather than me telling you to modify your config, I decided to update that plugin with some much needed improvements. I've pushed an update (v0.0.4) for that plugin that should give you a few more options. If you update the plugin on your install it should solve your issues. I have also re-written the description a bit, so take a look at that as there is now a new config option. Let me know if it works for you...

Can you also show us the config for the reject if larger plugin

Sounds like you have your stack configured incorrectly. Could you please share a screenshot of your library config and the plugin flow for the library

I'm a little confused. Can you not just get the FFmpeg command/params fro the log after processing a file? The official repo is on the official branch https://github.com/Unmanic/unmanic-plugins/tree/official/source%2Fencoder_video_hevc_qsv You can also install the Unmanic desktop launcher on windows if you don't want to muck around with wsl and docker.... https://github.com/Unmanic/unmanic-desktop-launcher/releases/tag/v0.1.2

I forgot to respond here sorry. Did you log back in yet? The server was undergoing maintenance this week. I did my best not to affect anyone, but it obviously did affect you sorry.

I finally got around to installing this to replace my Grafana stack. This is really well put together man. Awesome work! I'm a big fan of AIO containers on NAS devices. It takes the effort out of setting up the application. We are not here using Unraid so we can pretend that its an EC2 instance or VPS. This is a home NAS and your Docker image along with Unraid template has made this setup stupid simple and really clean on my Unraid dashboard. Thanks!

These are all variables. When you add them you can modify the ports that internally the services start on. Port mapping on this template is not going to change anything as the container is running on the host network so it shares the same port availability as the host

Start by trying to probe those files manually from a terminal: ffprobe -show_streams -print_format json /path/to/file.ext If that fails, the issue is not with Unmanic or the plugins. If that does give you an output I will need to think further on what it may be...

So what password keyring exactly do you want added. And how do you configure it to auto-unlocks?

You can set any of the ports with there variables: PORT_SSH="2222" PORT_VNC="5900" PORT_AUDIO_STREAM="5901" PORT_NOVNC_WEB="8083" PORT_AUDIO_WEBSOCKET="32123"

You can add your own container init scripts to install any keyring software that you need

I recommend setting up a VPN for this.

You have not plugins enabled on your library

If you enable debugging, you will get a better view of why it's not being added in the logs.

Thanks for the report. I've pushed an update to fix this issue for you

What branch are you on? Staging or latest for the docker image tag?

Have you recently updated the docker image? I published a hotfix to the main branch a day or so ago to fix a bug with the `.unmanic` files created in the directories. These are being migrated to JSON, but JSON by default is case sensitive while the INI parser being used previously was not. To maintain compatibility I need to ensure the keys being used in these files are case insensitive. So the fix I pushed the other day does this and should convert any files generated in the past few days since 0.2.0 was released to update all the keys to lowercase. If you have not updated in the past couple of days, please do so and clear the pending task queue.

Something has gone wrong with the settings .json file. In your container appdata, edit the file in .unmanic/config/settings.json (or just delete it). The key that is wrong or missing is "get_schedule_full_scan_minutes"

Shortly, I will be creating a new release for Unmanic. This new release has some big changes to how libraries work along with some really cool new features. This update will require that you reconfigure your library settings. If this is something that you do not wish to do, I suggest that you do not install this update. Edit: Release v0.2.0 published. https://github.com/Unmanic/unmanic/releases/tag/0.2.0

I can possibly help... How did you setup the server to that /dev/dri was available in unraid?

If I had to guess without knowing what you have setup, the proxy is not configured to support a websocket. In nginx you need to add "proxy_http_version 1.1;"