Joshndroid

I used the terminal commands to modify the postgres database when i first did it and on the subsequent 2 other times i remade the database for use across 2 different unraid boxes. I havn't had a necessity to redo it in a fairly long while. The password needs to also be 'kemal' so its both the USER and PASSWORD. Its weird and picky as all buggery. But you can see this within the docker-compose on their github. They also state that the initial migrations are all based on the user... if your putting the password as nothing potentially your not getting it setup right from the beginning I have used pgadmin4 in the community apps to work with my postgres container I have been able to setup users, backup/restore the specific invidious database just fine. Currently the invidious is using postgres 13... with a look to move to 14. I have used it with 14 however based on some of their issues with 14 I jumped back to my previous 12.5 postgres installation. I understand your frustration, however unless you can spot an actual error in the instructions its difficult for me to fix it as it is what worked for me and others on here up till your attempt. I had only been using unraid for a few months before getting this one to work. As you can see in this thread I have also taken in a lot from the community with fixes, suggestions, etc which I welcome.

Looks like you havn't set up your postgres container properly today at 18:21:16Unhandled exception: Error opening file with mode 'r': 'config/sql/channels.sql': No such file or directory (File::NotFoundError) _____________________________________________________________________________________ Invidious uses compose, we have to break them up into their component dockers, essentially. Invidious as part of their process runs a few files to setup their postgres container inline, we have to do it manually. see here it uses these files located here which is where i got the giant list for the postgres setup from. They havn't been changed in 17 months so it would be safe to assume they are still the same.

Interesting side note RE Invidious Database I see that within invidious they are using the latest postgres version/container (14).... I have gone through and migrated my database/s from postgres 12.5 to 14 and all seems to be working well. I used pgadmin4 container back up and restore the database (and others i had in there like nextcloud).

Honestly no real idea at this point. I cant say I have the same issue (which is know sounds annoying when yours broke), as mines still working with no changes made since my last update about it here. Just updating when required, one of which was last night for me. Is your postgres docker also in good health an running? Is your cache drive in good health?... The last time i had some weird docker issues when trying to update which would then fail and break my stuff was my cache drive was corrupted, going into read only mode and needed a full wipe/restore to work again.

My guess is that you would need to setup SMTP as well so it actually sends something.... Adding just an email wont do anything. Just did a quick google and see this which within the comments, essentially says the same. https://github.com/sabre-io/Baikal/issues/1014 I set all my accounts up through the admin panel with the admin user so didn't bother with email invites. it took a few seconds to setup within the admin panel...

Just as a note for anyone wondering. I have updated both my rigs to the 6.10 stable (well now its 6.10.1) and all the dockers are still working as intended. Simple upgrade and nothing was needed to be modified or changed

I probably annoyed the heck out of Roxedus messaged them everywhere lol But in any event the scrutiny template has been updated - https://github.com/selfhosters/unRAID-CA-templates/commit/7c04c10de005b2973536d83a50caf93ee7a60100 Hopefully see the merge in on the unraid side for the updated template soon

I recieved a reply from analogj on reddit as follows; I have pointed him to the direction of @Roxedus on his github page so he can get in contact and hopefully get this sorted asap and us back to receiving updates. tagging @ijuarez as you were interested.

It would appear Scrutiny dev has pulled his images from dockerhub and may have them elsewhere https://github.com/AnalogJ/scrutiny https://hub.docker.com/r/analogj/scrutiny <- 404's I have messaged the dev on reddit for some confirmation It would appear the base repo is - ghcr.io/analogj/scrutiny (based on his docker compose in the github linked above)

Hey ICH777 I am aware the container it did not kill my flash drive just more the annoyance that the forced reboot after the container hung was the final nail in the coffin for it. Its possible regarding H265. I basically just ticked all and figured nothing would happen if it tried rather than potentially lock up I didnt even get to play anything or transcode anything. I did the initial setup, exposed a few more paths to videos, etc which all showed fine in setup. I then completed the rest of the setup. It hung after being in settings when trying to go back to the desktop.. it spiraled from there lol.

So I tried to set this up yesterday got it all installed however it sorta hung after I enabled transcoding for NVENC. I have a 970 in my server which has been working fine in Plex. I was then unable to force the container to shut down through GUI or Terminal Had to manually force a reboot, and lucky me my flash drive took the brunt and died lol. I have restup my server and am not sure if it is wise to try again. I did tick all the encoding options after selecting NVENC. I am wondering if anyone else has seen this? Am I missing something. I am a little hesitant to try again after my whirlwind of an evening last night lol

I think at this point ill just wait until i get the email support reply from unraid.

More mucking about than should be necessary. I am looking forward to the login that is eventually coming so its just tied to my account I have tried with the whole contents of the /config over, no option to start a trial So I deleted the key file and the trial file from /config which now just says missing key file... lol. Going to copy the trail key back to see what happens Edit - nope didn't work either... lol

So i've just had my second USB die in the span of 12 months. Now locked out of my server, which is annoying with the needing to email support regarding fixing my license, sigh. But i have sent the email. What I am asking is has anyone used a Server Sata DOM as their 'flash drive' to potentially get some better longevity out of a flash drive. I have tried various brands that I can actually purchase around me (as they always die when you dont want it too) and am thinking of shelling out a bit extra to hopefully have some space between another dang USB failure.

Stumbled on this after getting my own webmail lite working and wanting a pro one... I must not have searched properly the first time. I see you haven't "volume" the /data/settings for easier accessing the config or modules files (https://afterlogic.com/docs/webmail-pro-8/configuring-webmail/advanced-configuration) I am wondering how your accessing /data or where it is situated within the docker as within the console I can't seem to find/access it.

I think at this time I am going to remove this template. I didn't dive enough and I think there are more issues with the docker, than with their manual install. It appears their docker is basically not up updated (the docker hub instance lists 1 year... and the associated believed docker github repo hasnt been updated in 3 years, whereas the program git was updated 2 days ago.... Those errors your seeing are more to do with the container than the template/docker program from what I understand and without forking the project and updating it I have a feeling i can't fix it with a few commands. You are more than welcome to grab the template and have a play (or i can send you it) I ended up over at Afterlogic Webmail Pro and paid for a license... It does everything I need (webmail and able to link further IMAP accounts) and worked 1st time for me.

Lucky me... Of Course it changes around the time i implement it lol. RIMGO Update 25/4/22 I have updated the template and updated the docker container and mine seems to be working with the new changes. I have pushed them over to the template here - https://github.com/Joshndroid/joshndroid-unraid-docker-templates/commit/0765b6795bd8720514f0a0b3c5fd09c296990984 As always happy for any pull requests.

Update 24/4/2022 Have added Cypht to my Repo. I have been using Thunderbird in docker to try and keep everything central however it is a bit clunky. I was searching around for an all in one IMAP webmail program. A lot of them are tied to a single webserver which is not what I wanted. There is only a docker compose for this and appears to bundle a mariadb in with it. With this container I managed to decouple it from mariadb so that you can use your own... Which of course needs to be set up before you are able to use this one correctly. I can't say I have had much time with this one

Update 22/4/2022 Have added a imgur front end named rimgo (a fork of rimgu rewritten in go). Most of the stuff is there just waiting for acceptance into the community apps. probably more useful for using with something like libredirect....

Probably need to look at changing the WebUi in "advanced view" as well as change the container port in port.

Good to see you got this working for you. I typically use Nginx Proxy Manager, saves some of the mucking about that i had to do with swag but each to their own of course :)

Bibliogram Template Update 17/4/2022 Had to swap the repo from the original which has gone 404..... Maybe the maintainer was over it. Switched to schklom/bibliogram on my local install with no issues. Updated the Template with following to reflect changes <Repository>schklom/bibliogram</Repository> <Registry>https://hub.docker.com/r/schklom/bibliogram</Registry> While i don't actually use it, hopefully for those that do it continues to work for you as well with the updated template/repo in the future

Plz See here - https://next-auth.js.org/configuration/options#secret (basically openssl rand -base64 32 The NextAuth Secret is referenced in the github readme of the troddit source - https://github.com/burhan-syed/troddit

Thanks mate for picking that up. I have updated the Nitter template as a result https://github.com/Joshndroid/joshndroid-unraid-docker-templates/commit/6bc175d7d5a2ad3f040e6c5c715bbd69d30dceef

If you are using firefox also try and see if turning off 'enhanced tracking protection' (The little shield thing in your URL bar). I find sometimes with some self hosted stuff it causes issues, where turning it off for selected self hosted stuff will fix it up.