Joshndroid

Have a look at your config.yml file in the invidious console. Check the content of the file for hostname/database lines (from memory its right up the top) That error is basically when invidious can't find the database. Its picky as heck. I had a feeling that there may be some teething issues. I wrote the guide mostly well after I had set my instance up. There is potential I have missed a step. I am unable to be at my PC at present but will take another look when I get home.

Is your postgres container on the same network as your invidious? I am reverse proxying mine through a network named proxynet both postgres and invidious are on this network type.

What is the name of your postgres container? I had mentioned above that I changed my postgres12.5 or postgres10 to just postgres. Give that a try and let me know how you go.

this post is reserved for potential future use 3

this post is reserved for potential future use 2

***INVIDIOUS - Please note that Google is actively trying to break any sort of privacy/adblocking, etc. YMMV and issues are cropping up quickly. Further setup may be required (Page 7 is a help)*** also see - Invidious Docker Setup Post (including database setup that MUST be undertaken) Firstly I just want to take the opportunity to shout out @A75G . They have provided a second method for setting up Invidious that may be preferential to other users. They also have run through this following guide in their own setup of Invidious. Invidious is a tad tricky in that it has a number of config settings that are needed as well as being fairly hard coded into other areas. Invidious can also be a bit buggy at times. I have been running Invidious as a docker for approximately 4+ weeks with constant updates occurring essentially daily. I understand that from a security standpoint this may not be preferential for systems being truly exposed to the internet. I had to weigh up the ease of use for users as well as the security implications. For me, if someone has access to my database in my setup, I have far more to worry about than the invidious docker container. For those instances requiring more security I would look at doing some manual setup in various areas to provide some more security please see here for further https://docs.invidious.io/Installation.md specifically the 'Set up PostgresSQL' section. You can utilise the standard template that is bundled into the docker community apps. This will provide the basic mostly ready to go setup experience with minor changes required to the config file prior to starting invidious for the first time. To generate the config file run these commands in the console mkdir /mnt/user/appdata/invidious mkdir /mnt/user/appdata/invidious/config wget -O /mnt/user/appdata/invidious/config/config.yml https://raw.githubusercontent.com/iv-org/invidious/master/config/config.example.yml Then setup your config.yml with your settings prior to starting the container. Note if you have set up your appdata folder under the 'shares' tab to be exposed you can edit this file using a text editor such as atom. If you don't wish to use this method you can edit the file within the main console and navigate to /mnt/user/appdata/invidious/config/ and then use 'vi' editor to edit the config.yml For example; I have this config areas changed; Line 14 host: (set to the IP address of your postgres installation - make sure this is on the same network as your invidious install) This should be enough to get you going on a http accessed instance NOT behind a reverse proxy. If you wish to utilise a reverse proxy utilise these config lines as well Line 79 external_port: (set this to your reverse proxy port, for me its 443) Line 98 domain: (set this to your preferred domain, such as example.com) Line 109 https_only: (set this from false to true) NOTE - Please note that there are further configs that can be set within your template. These can be located within the invidious docs here - https://docs.invidious.io/Configuration.md Please note that the HMAC key is required as of July 1 2023. It is essentially a user generated string value that is unique to each installation. This will need to go into your config.yml under the 'hmac_key: "CHANGE_ME!!"' section. See https://github.com/iv-org/invidious/issues/3854 You can generate your string with a line such as; 'pwgen 20 1 or openssl rand -hex 20' Network Settings Note I am personally using a custom network 'proxynet' within unraid. I use this in conjunction with my reverse proxy to handle the SSL certs for my domain. Using a custom network enables the ability to handle DNS between containers when both on the 'proxynet' network. thanks @Syk0tic If you are wanting to use the br0 (or I imagine host network would be the same for this as well) please make a DNS entry for the domain 'postgres' on your DNS resolver. I use pi-hole on my network and was able to go into the setting 'local DNS' add 'postgres' to the domain field and then add in the 'IP' of the postgres database (which was also on br0) and invidious works as intended. For those wishing to bridge I can't recommend this method until i do some further research. Invidious Docker Database Setup Instructions (postgres) Note - Invidious is rather picky when it comes to the database labels/naming conventions. I had tried in the past to modify these values which would lead to the container not functioning at all. I had mentioned it when talking with the Invidious devs and they have acknowledged that the names are essentially ‘hard coded’ and basically from my understanding that you may as well leave them as is unless you want some headaches. I had utilised postgres10 in the past however I have this working with postgres12.5 as found on the Community apps page. I have the postgres12.5 container named postgres within the docker page of that specific docker. Once you have your postgres database installed we need to create the invidious database Lets assume that you have created the initial postgres database up with postgres as your user psql -U postgres CREATE DATABASE invidious; create user kemal with encrypted password 'kemal'; GRANT ALL PRIVILEGES ON DATABASE invidious TO kemal; exit This has setup the required database of ‘invidious’ with the required username and password Now we need to log back into the required database and create further entries for invidious to function correctly with the database. These commands can be found within each ‘.sql’ file located at https://github.com/iv-org/invidious/tree/master/config/sql First log into the container with the new user and to the database psql -d invidious -U kemal Now you need to copy these commands. You can either copy each paragraph section from the || CAPS LOCKS all the way to the first ; || OR you can copy the whole code block and paste into your terminal (I have tested this as working on a fresh setup) CREATE TABLE public.annotations ( id text NOT NULL, annotations xml, CONSTRAINT annotations_id_key UNIQUE (id) ); GRANT ALL ON TABLE public.annotations TO kemal; CREATE TABLE public.videos ( id text NOT NULL, info text, updated timestamp with time zone, CONSTRAINT videos_pkey PRIMARY KEY (id) ); GRANT ALL ON TABLE public.videos TO kemal; CREATE UNIQUE INDEX id_idx ON public.videos USING btree (id COLLATE pg_catalog."default"); CREATE TABLE public.channel_videos ( id text NOT NULL, title text, published timestamp with time zone, updated timestamp with time zone, ucid text, author text, length_seconds integer, live_now boolean, premiere_timestamp timestamp with time zone, views bigint, CONSTRAINT channel_videos_id_key UNIQUE (id) ); GRANT ALL ON TABLE public.channel_videos TO kemal; CREATE INDEX channel_videos_ucid_idx ON public.channel_videos USING btree (ucid COLLATE pg_catalog."default"); CREATE TABLE public.channels ( id text NOT NULL, author text, updated timestamp with time zone, deleted boolean, subscribed timestamp with time zone, CONSTRAINT channels_id_key UNIQUE (id) ); GRANT ALL ON TABLE public.channels TO kemal; CREATE INDEX channels_id_idx ON public.channels USING btree (id COLLATE pg_catalog."default"); CREATE TABLE public.nonces ( nonce text, expire timestamp with time zone, CONSTRAINT nonces_id_key UNIQUE (nonce) ); GRANT ALL ON TABLE public.nonces TO kemal; CREATE INDEX nonces_nonce_idx ON public.nonces USING btree (nonce COLLATE pg_catalog."default"); CREATE TABLE public.users ( updated timestamp with time zone, notifications text[], subscriptions text[], email text NOT NULL, preferences text, password text, token text, watched text[], feed_needs_update boolean, CONSTRAINT users_email_key UNIQUE (email) ); GRANT ALL ON TABLE public.users TO kemal; CREATE UNIQUE INDEX email_unique_idx ON public.users USING btree (lower(email) COLLATE pg_catalog."default"); CREATE TABLE public.session_ids ( id text NOT NULL, email text, issued timestamp with time zone, CONSTRAINT session_ids_pkey PRIMARY KEY (id) ); GRANT ALL ON TABLE public.session_ids TO kemal; CREATE INDEX session_ids_id_idx ON public.session_ids USING btree (id COLLATE pg_catalog."default"); CREATE TYPE public.privacy AS ENUM ( 'Public', 'Unlisted', 'Private' ); CREATE TABLE public.playlists ( title text, id text primary key, author text, description text, video_count integer, created timestamptz, updated timestamptz, privacy privacy, index int8[] ); GRANT ALL ON public.playlists TO kemal; CREATE TABLE playlist_videos ( title text, id text, author text, ucid text, length_seconds integer, published timestamptz, plid text references playlists(id), index int8, live_now boolean, PRIMARY KEY (index,plid) ); GRANT ALL ON TABLE public.playlist_videos TO kemal; Then you have to exit exit Now your database should be correctly setup. Maintaining the Database (which does get large over time) please see the steps within the documentation - https://docs.invidious.io/Database-Information-and-Maintenance.md

This is the support thread for the docker templates I have added to community apps. You can find my templates on GitHub at - Joshndroid I am more than happy for some help/pull requests Redlib An alternative private front-end to Reddit. The source is available on GitHub at Redlib-org/redlib Baikal Baïkal is a lightweight CalDAV+CardDAV server. It offers an extensive web interface with easy management of users, address books and calendars. It is fast and simple to install and only needs a basic php capable server. The data can be stored in a MySQL or a SQLite database. The source is available on GitHub at Sabre-io/Baikal The source for the docker is available on GitHub at Ckulka/baikal-docker You can find my community apps page for Baikal at - /link If you would like to roll-your-own docker straight from docker hub, have a look at the guide - Joshndroid/Baikal-Guide NOTE - Baikal seems to be a bit of a pain now with permissions on the creation of the docker. It is wise to create the /appdata folders prior to the installation of the application via the template to stop these permissions errors. Please see here for further Invidious An open source alternative front-end to YouTube The source is available on GitHub at iv-org/invidious The source for the docker is available on Quay.io at invidious/invidious You can find my community apps page for Invidious at - /link For setup assistance please see the Setup Post Rimgo Self-hosted frontend for imgur. Rewritten in Go. The source is available on github at video-prize-ranch/rimgo Microbin MicroBin is a super tiny, feature rich, configurable, self-contained and self-hosted paste bin web application. It is very easy to set up and use, and will only require a few megabytes of memory and disk storage. It takes only a couple minutes to set it up, why not give it a try now?. The source is available on github at szabodanika/microbin JustPix JustPix is a small read-only photo, video, and audio gallery for a local media folder. It is designed for Unraid and other Docker hosts where your media is mounted into the container as read-only storage. The app never uploads, edits, tags, deletes, or writes metadata to your media library. The filesystem is the source of truth. The source is available on GitHub - Joshndroid/JustPix FeaturesFolder and subfolder browsing Read-only media serving from /photos Images, videos, and audio files in one gallery Responsive browser UI with breadcrumbs, sorting, pagination, lazy thumbnails, and a lightbox Native browser playback for video and audio Cached image thumbnails and video poster frames in /data/thumbcache Optional local login gate backed by /data/config/users.json Reverse proxy support with ROOT_PATH Basic security and cache headers Apps previously supported but discontinued by developer Bibliogram, Troddit Apps previously implemented but discontinued by me Cypht

So i tried again and seem to have this working. I have attached some pictures to anyone who is playing along at home. I am unsure of its stability at this time. However if there is interest I may learn how to publish it to CA for others to enjoy. the appdata variable is set to the container /config I was able to use the reverse proxy to provide ssl which also works nice. There is a config file which i describe in the descrption that I have written in the box that gets cut off so ill post the contents of that into here. [Unit] Description=Nitter (An alternative Twitter front-end) After=syslog.target After=network.target [Service] Type=simple # set user and group User=nitter Group=nitter # configure location WorkingDirectory=/home/nitter/nitter ExecStart=/home/nitter/nitter/nitter Restart=always RestartSec=15 [Install] WantedBy=multi-user.target you could change the port 8282 to whatever may suit your host ports

Hello All, I have been looking at Nitter, basically a privacy focused twitter. https://github.com/zedeus/nitter It can be utilised along with RSS readers to give you a relatively nice, privacy focused twitter experience. I am running this within a VM just fine under docker however am unsure on how to move forward. the onliner in for running docker straight within a VM was - docker run -v $(pwd)/nitter.conf:/src/nitter.conf -d -p 8080:8080 zedeus/nitter:latest did have a crack in pulling in the docker from docker hub in CA. i had a play with the template. I setup variables = PUID = 99, PGID = 100 Host Port = 80 (Container Port: 80) Appdata config path = /mnt/user/appdata/nitter (Container path: /config) Within the github - https://github.com/zedeus/nitter It mentions that it needed a nitter.conf which I had placed within /mnt/user/appdata/nitter prior to first running of the docker. The container starts however no webgui is generated.

by me replying and you replying we have it here in the thread. it can be found now if people search. ¯\_(ツ)_/¯

I think you need a section for step involved in swapping a card (Nvidia for Nvidia). For example 970 out, 1030 in. I had asked a question in the forums with no answer, however; So for anyone who is playing along at home (in the future) 1. Turned off all the auto starts for docker and VM's to be on the safe side. 2. Shutdown unraid PC 3. Swapped out the 970 and in the 1030. 4. Power up server 5. Wait for full boot up, watching terminal output (as had hdmi plugged in) 7. Check in Nvidia plugin - new 1030 was recognised. 8. Update GPU info into the containers for plex, etc. 9. Remove then reinstall GPU statistics (for some reason this did not refresh with new info until I completed this). 10. Profit!!?????

Thanks mate, I like the concept so looking forward to your work on it further.

After some further looking it depended on the client running on the system... So once i started checking out the nightly client ferdi releases I could see more services listed (such as nextcloud calendar)

Thanks mate for the further work on this.

I tried your checkmk raw container and it locks up my docker when trying to stop the container... It wont stop or delete or anything of that nature. I had to force a reboot to get back control of the server. I had tried terminal as well to kill it and that didn't work. I gave it another crack a few days later and same result. Its on my no go list now based on those experiences. I thank you for all yoru work it just seems this container doesn't play ball for me.

I have just updated the repo in the original docker config template I had been using and seemed to work fine no issues thus far.

LoL... i have 12TB.... that isn't full.. I have about 400-500GB of pure important data that has multiple backups externally. I wouldn't mind increasing the drives from 3TB to 4TB drives but until they start to die or fill up i kind of dont see much of a point unless i grab 3 drives straight away to begin the process (ie the 2 parity drives and a single larger data)

Managed to get this up and working this afternoon; sqlite, ssl, reverse proxy, custom domain, smtp, all working a treat. I had checked ferdi out, rebuffing yet another service with a bunch of my data, prior to finding your container for the backend stuff. Love it. Thanks for the work and keep the updates coming one thing I do see is that the services offered are not as plentiful as those in their github or on their 'services' page

I would like to see xBrowserSync... "xBrowserSync synchronizes bookmarks across devices and browsers with end-to-end encryption" on privacytools.io. It also has an official docker page to track - https://hub.docker.com/r/xbrowsersync/api It can hook in with mariadb It is fairly browser agnostic and seems to handle bookmarks a bit more natively than those such as shaarli (which I am using now).

I have nginx attached to a proxynetwork, as originally advised within spaceinvaderone's lets encrypt video. I find this to work perfect. I have multiple dockers running just find while attached to proxynetwork What i can't seem to get to work is basically, nginx to redirect straight back to a lan address. Is it possible to hit nginx at 192.168.1.xx have have it kick you back out to a 192.168.1.zz address and supply a cert? (utilising redirect) I can hit nginx at 192.168.1.xx and push across to 172.1.1.yy and get SSL certs. What i am trying to do is utilise Nginx as my catch all and push it to either through to the proxynetwork 172....... addresses or redirect back to 192.168........ address if that it at all possible, mainly due to the fact that I cant get my VM to expose itself onto the proxynetwork for it to work that way as it is just not how it works

This Might be dumb lol : Can I use Nginx proxy manager to redirect to br0 Hey All, I have no idea if this is possible but thought I might ask. Is it possible to use Nginx Proxy Manager to redirect back to local IP for stuff hosted on VM with SSL I have Nginx Proxy Manager setup and can utilise it for things attributed to custom network 'proxynet' VM's are using br0 network of course. I wish to use it to redirect back out to a VM address on my local lan, providing it a domain and a SSL cert on the way. Is this even possible?

As dumb as this may sound; It may seem that the generation of port may be playing a part in why it dies. I noticed in the log this error - usbhid-ups[7753]: nut_libusb_get_interrupt: Input/Output Error. I read a very old post in which people were advising that nut was using an old libusb which is deprecated and been replaced. It also advises within that the newer libusb it addresses deficiencies with USB 2 and 3... source: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810449 On flowing through i can see that this is still an open issue on the NUT's github https://github.com/networkupstools/nut/issues/300 Considering I don't have much to lose at this point i noticed I had the USB plugged into a USB 3 port on the motherboard rear (it may have been even a 3.1 port, hard to tell colour at the back in the dark). Anyway I switched the USB to the keyboard/mouse usb at the top of the motherboard and voila, hit refresh and UPS came back. Something it has never done before after it dies. Something to think about when using the USB plug from your UPS

I have a CyberPower 1600 UPS. 'VP1600ELCD' which is connected via the supplied USB plug. It worked fine in the built in UPS section. I want NUT so I can also tie it in with home assistant. Anyway.. I have it up and running and can see it in home assistant. My problem is that it seems to just die randomly. Usually a reboot will fix it however sometimes it again just dies. Basically it it is working as intended and then it just stops reporting anything and shows all '-' and N/A in the little page footer bit. I try a 'reload' using the button in the NUT settings but it doesn't come back. I have set the built in UPS settings as noted in the fist post. Anything else I can try? Any ideas

I have found much better success with the dns challenge

Righto all. RE - 502 Gateway error Just a quick psa that had me scratching my head for a few days and cause me to install/reinstall this and other containers that doesn't get mentioned in many videos on container setup when using a custom proxy network wondering why it would work fine for hours then break giving 502 bad gateway errors. Set your container IP's as static within unraid container edit page as they are ultimately static in the proxy manager. So whatever ip you designated the redirect ip to, in my case 172.18.0.5 is what you need in the container edit page under the ip. Can't believe I was so oblivious to this yet have static ips for all sorts of things. I was under the impression that unraid would just keep giving containers the same ip for some strange reason. I'm sure heaps of people know this one but had an epiphany this morning after my dramas. This container kicks butt btw