darkrom

Works great after the update thanks. Only question is how would you restore just one app? Say I wanted to restore just Bitwarden, what would the process be? Thanks again!

The line number was 196 sorry, just updated my post to include it. I ran that command in terminal and got back the following: -rw-r--r-- 1 root root 81M Dec 4 06:34 /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log It does appear on the backup status page but the backup now button is greyed out and it is not running scheduled backups either. So as far as I can tell I have no way to run a backup at the moment. I copied one of my successful backup TARs from the older version to another location and then deleted them all from the appdata backup folder to see if that made any difference and it did not.

I am getting the following just Now after updating to the new version: "Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 84473952 bytes) in /usr/local/emhttp/plugins/ca.backup2/include/backupExec.php on line 196" Anyone know what to do to resolve this? Thanks

I'm going to nuke invidious and the database and set them up fresh. It really was rock solid once it was up and running, and I did it once before so I can do it again. Thanks!

I am using 12.5, I actually did restore the appdata using that, which makes it really confusing to me that its not working. I have every other app working but this one. I will have to poke around a little more but then I'll share my redacted config.yml if I can't get it. Thank you for this project by the way! This is one of the absolutely essential containers for me.

I am trying to rebuild invidious after a server issue I had, its the last app I can't get running properly. From unraid webUI if I open it I get: {"status":"OK","version":{"major":2,"minor":9,"revision":18}} If I go to the url that previously worked in NPM I get 502 Bad Gateway. If I go to the invidious logs I get: [production] Invidious is ready to lead at http://0.0.0.0:3000 Does anyone know what I'm doing wrong? I really want to get this back up and running.

It is the same config.yaml that was working before one of the updates and then it stopped. It is located in /mnt/user/appdata/invidious/config/config.yml I'd love to get this working again. I'll try to find a testing site.

I'm seeing the following in my logs. Latest update. It was once working fine via reverse proxy so I don't want to change anything on that end, it seemed to stop working with one of the container updates. Unhandled exception: could not find expected ':' at line 100, column 1, while scanning a simple key at line 98, column 1 (YAML::ParseException)

I'm having the same issue with Invidious. I did notice the 2 configs after reading here, deleting one did not fix it. This was all working correctly, one of the updates broke it. I can pull logs if its helpful but I'm just reporting it. Happy to wait for a fix.

No luck. Maybe I'll reach out to binhex, I must have done something wrong but I don't see what.

Its working on your container! Wow so simple and I never would have thought to try that thank you. I guess I should swap from binhex to yours on both!

Absolutely I'll give yours a rip. Thanks for the help lets see how it goes!

I am using binhex plex and binhex jellyfin. With plex I do have plex pass, but at this point I've been mostly just trying to get it working in either. I see this in jellyfin so I know its transcoding, purposely picking a 4k to 720p in this case. @alturismo this seems to be the jellyfin version of that screen in emby, but it does confirm it is transcoding.

I can't figure out what I'm doing wrong but it seems like everything should work, but no luck. Please see the album below this is driving me nuts. This should show every relevant setting. I have the same config in plex and neither plex or jellyfin is showing any GPU usage when it should be transcoding, but the CPU usage is still climbing as high as ever. I must be missing something and could really appreciate some help! https://imgur.com/a/5xEfXdv

I got invidious running great locally 192.x.x.x but I am unable to get it working on NGINX proxy manager. Anyone got it working and mind sharing your config? I have other stuff like jellyfin and Bitwarden working so I have a fairly good understanding on NGINX proxy manager. Ideally I'd like to redirect it to a full base domain like. https://example.com. previously all of my reverse proxied services are subdomains like Bitwarden.example.com