2 hours ago, i_max said:

Hello,

 

I've installed Invidious. I'm able to host it via NGINX Proxy Manager. However, I'm not able to set quality to dash (hd720 works), and I'm getting the "The media could not be loaded, either because the server or network failed or because the format is not supported." error.

 

I'm wondering if anyone else has this issue. I had followed the instructions to use postgres 12.5 as well as setting up the database as per original post. Since everything else works, I'm assuming most things are set correctly. Here is snippets of my config file which I'm not 100% sure about:

 

https_only: true

external_port: 18443

hsts: true
disable_proxy: false

force_resolve:
port: 3000

host_binding: 0.0.0.0
pool_size: 100

 

The proxy video option, doesn't tend to do anything in the settings in the GUI wrt the error above. I'm really trying to get the videos to play in 1080. To add a few more details, I've Pihole setup in the network. In the network port 80 is blocked, and invidious has Authelia authenticating before being directed to the gui.

 

 

 

 

 

Yeah i can't seem to get anything above 720 to work either... its been like that for a long while TBH.

I don't know if its part of Youtube trying to crack down on anything or if there is a setup issue.

I have tried various settings/etc but can't seem to get any higher.

If you find anything please let us know

 

On 5/8/2024 at 11:32 PM, Joshndroid said:

 

Yeah i can't seem to get anything above 720 to work either... its been like that for a long while TBH.

I don't know if its part of Youtube trying to crack down on anything or if there is a setup issue.

I have tried various settings/etc but can't seem to get any higher.

If you find anything please let us know

 

I was able to get it to work I had to set 'external_port' to 443 and few restarts. I was almost about to move on, but its working fine. I'm working on setting the firewalls so my hosted instance can work only via VPN. Good Luck, let me know if you get stuck after trying this.

5 hours ago, i_max said:

I was able to get it to work I had to set 'external_port' to 443 and few restarts. I was almost about to move on, but its working fine. I'm working on setting the firewalls so my hosted instance can work only via VPN. Good Luck, let me know if you get stuck after trying this.

 

Yeah I've had that same thing set as well for a while but still no dice.

I do have my stuff fairly locked down behind a VPN, so it could be something else in my setup here at home that is impacting that.

I think they might have busted us?

 

Quote

Couldn't send request to Reddit: error trying to connect: dns error: failed to lookup address information: Name does not resolve

 

Reddit is up and running just fine.

On 5/30/2024 at 7:51 AM, stry8993 said:

I think they might have busted us?

 

 

Reddit is up and running just fine.

 

Which program are you talking about? You may need to create an issue or check for an already made one in the respective project github/gitlab/etc

Am I doing something wrong here with Redlib?

 

Extra parameters I have this:
--restart=unless-stopped --env-file /mnt/user/appdata/redlib/.env

 

This inside .env file I have this 

REDLIB_DEFAULT_SUBSCRIPTIONS=sub1+sub2+sub3

 

It doesnt defaulting to this setting. Is the format of the string above wrong? Or does anyone have any ideas?

1 hour ago, klppl said:

Am I doing something wrong here with Redlib?

 

Extra parameters I have this:
--restart=unless-stopped --env-file /mnt/user/appdata/redlib/.env

 

This inside .env file I have this 

REDLIB_DEFAULT_SUBSCRIPTIONS=sub1+sub2+sub3

 

It doesnt defaulting to this setting. Is the format of the string above wrong? Or does anyone have any ideas?

Hey mate,

 

if you're trying to parse the env file... it would appear it would need to be added as both a path (so the structure /mnt/user/appdata/redlib is created) then as a variable (so the file is associated)...

***FORGOT TO MENTION THIS IS FOR INVIDIOUS***

 

I've got everything up and running, and it's currently working but I'm having one issue. When I enable DASH it breaks all videos. Literally nothing will play. I have done everything within my power to research everything I could to figure it out and I can't find anything. The logs are unhelpful because all they are showing is:

[warn] i18n: Missing translation key "auto"

which may or may not even be related to my issue. I don't even really know what information to provide in order to assist in troubleshooting, but I don't mind providing anything that's required.

I'm on the latest version of Unraid.

I'm on the latest version of the invidious docker container provided by JoshNDroid

I'm using PostgreSQL 14

I'm using a custom docker network for all my docker containers

I'm behind a NPM reverse proxy (which works fine)

I'm not opening it up to the internet, I'm only making it accessible via a wireguard VPN connection for myself and my wife.

 

Any insight would be greatly appreciated, this is not an emergency just more of a frustration. As stated above it's working, I just hate being limited to 720p while all these other posts I'm reading, everyone's like "Why isn't DASH enabled by default? It's so amazing!". I would like to make that decision myself if possible, but so far it doesn't look promising...

Edited September 23, 20241 yr by frogweh
Forgot to specify the application

@Joshndroid I was able to make it work I had "The media could not be loaded, either because the server or network failed or because the format is not supported." since 3 days. Youtube seems made adjustment so I've added this new container https://github.com/iv-org/inv_sig_helper  who is related to this https://github.com/iv-org/invidious/issues/4734 and https://github.com/iv-org/invidious/issues/4947.

 

Now it's working again no quality limited or something else. 

 

2 posts below I've put each step to make it work on my side but maybe there's something more easy to do.. 

 

 

 

Edited September 26, 20241 yr by HuSoS

Hi @HuSoS that sound good. How have you done adding the new container?

Can u maybe give an explanation?

Thank you!

Or maybe you share some screenshots from you inv-sig-helper container config?

Edited September 26, 20241 yr by hando

Hi @hando, well I'm not a pro and maybe there's an easier way to do it here is what I've done..

 

They adjusted original installation doc https://docs.invidious.io/installation/   but from Unraid it's not as straight forward. 

 

Step 1. Stop Invidious container

 

Step 2. You need to generate 2 value (visitor_data and po_token) from a computer or server that use the same IP as your Invidious instance.

In Unraid you can open a terminal and run command below - In the log you'll see both value (Keep it for later)

docker run quay.io/invidious/youtube-trusted-session-generator 

 Or you can follow those step that require Python installed - https://github.com/iv-org/youtube-trusted-session-generator?tab=readme-ov-file#tutorial-without-docker

 

Step 3.  In Unraid console run
OR you can check alternative to replace Step 3-4. From replies bellow there's 2 alternative explain by lining7333 or Flier1K. Without portainer or directly on docker-compose.

 

docker run quay.io/invidious/inv-sig-helper:latest

Step 4.  We need to tweak some value in inv-sig-helper container I've used portainer. First inv-sig-helper and invidious need to be on the same network in portainer you can change network in the network tab. Ex; Bridge etc...

In command & logging tab the default command is ["--tcp", "127.0.0.1:12999"] in my case to make it work I had to change it to the internal docker ip (First image) ex;  '--tcp' '172.17.0.17:12999' or '--tcp' '0.0.0.0:12999'  (Then redeploy this docker)

 

 

 

Step 5. We need to truncate our "video table" in the database it's can be done with adminer or in command.

https://github.com/iv-org/invidious/issues/4947#issuecomment-2373119661

 

 

Step 6. Modify config.yml file in invidious folder, add and fill these 3 values from our previous step.

signature_server:  [DOCKER-INTERNAL-IP-EX;172.17.0.17]:12999
visitor_data: key (from step 2)
po_token: token (from step 2)

 

EDIT: Not needed anymore to be on master branch - Shoud Keep latest
Step 7. Before restart invidious docker we need to replace Repository quay.io/invidious/invidious:latest to  quay.io/invidious/invidious:master  It's what they ask https://github.com/iv-org/invidious/issues/4734#issuecomment-2362314357

 

 

 

As I said I'm not unraid/docker expert so you may encounter some issues but hope can help some of you!

 

 

EDITED : Added mention alternatives on step 3 for lining7333 & Flier1K from their replies.

 

Edited February 14, 20251 yr by HuSoS
Correct some typo and add images

@HuSoS thank you i`ll try with that

@hando Post is fully edited with some references posts(github, official doc) and screenshot hope you can make it work. 

@HuSoS thx for the tutorial, I had same issue for last several days but now it works again.

Although I had to try several times to get it working again somehow.

On 9/27/2024 at 9:07 AM, HuSoS said:

@hando Post is fully edited with some references posts(github, official doc) and screenshot hope you can make it work. 

 

Mate amazing job.

I have not got to running through your steps but what I may do is just link to these posts from the setup post/s.

Thanks for helping us all out

 

As a side note... It's really getting to the point that these privacy focused front ends are under attack by the 'line must go up' crowd.... it's a shame and making everything difficult

Edited September 29, 20241 yr by Joshndroid

For Invidious: Can anyone share screenshots of a fully working setup of their invidious and inv_sig_helper containers? Preferably without Portainer, since I don't have that.

 

I followed the initial Invidious setup guide from Joshndroid, and postgres and Invidious seemed to work at that point (except, of course, I couldn't play videos in the Invidious GUI due to that recent* Google block), But once I tried to add in inv_sig_helper and modify Invidious, I kept getting constant errors. I kept track of all the different ways I've tried to get them to work so far, and it adds up to 24 attempts in total, so I'm at a loss. I'm sure it's something simple, but I can't crack it.

Edited September 30, 20241 yr by lining7333

@lining7333 What is the error log on Invidious and inv-sig-helper? 

Hey right before you replied, I finally got it working with the help of Docker compose. (I didn't even check the error logs because I'm not a smart person!) I'll update this post in a bit with screenshots of my compose file.

 

EDIT:

 

Here's my working compose file. I was also going to include a screenshot of my postgres config, but I realized it's essentially the same as the default 12.5 template in Community Applications, along with Joshndroid's exact instructions for setting the container/database up correctly.

 

services:

  invidious:
    network_mode: bridge
    container_name: invidious
    image: quay.io/invidious/invidious:master
    # image: quay.io/invidious/invidious:latest-arm64 # ARM64/AArch64 devices
    restart: unless-stopped
    ports:
#      - "127.0.0.1:3000:3000"
      - 3000:3000
    environment:
      # Please read the following file for a comprehensive list of all available
      # configuration options and their associated syntax:
      # https://github.com/iv-org/invidious/blob/master/config/config.example.yml
      INVIDIOUS_CONFIG: |
        db:
          dbname: invidious
          user: kemal
          password: kemal
          host: [my Unraid IP address]
          port: 5432
        check_tables: true
        signature_server: 172.17.0.20:12999
        visitor_data: [my visitor_data string]
        po_token: [my po_token]
        # external_port:
        # domain:
        # https_only: false
        # statistics_enabled: false
        hmac_key: [my hmac_key]
    healthcheck:
      test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/trending || exit 1
      interval: 30s
      timeout: 5s
      retries: 2
    logging:
      options:
        max-size: "1G"
        max-file: "4"

  inv_sig_helper:
    container_name: inv_sig_helper
    network_mode: bridge
    image: quay.io/invidious/inv-sig-helper
    init: true
    command: ["--tcp", "172.17.0.20:12999"]
    environment:
      - RUST_LOG=info
    restart: unless-stopped
    cap_drop:
      - ALL
    read_only: true
    security_opt:
      - no-new-privileges:true

 

Edited September 30, 20241 yr by lining7333
added compose file

6 hours ago, lining7333 said:

Hey right before you replied, I finally got it working with the help of Docker compose. (I didn't even check the error logs because I'm not a smart person!) I'll update this post in a bit with screenshots of my compose file.

 

EDIT:

 

Here's my working compose file. I was also going to include a screenshot of my postgres config, but I realized it's essentially the same as the default 12.5 template in Community Applications, along with Joshndroid's exact instructions for setting the container/database up correctly.

 

You are a lifesaver. I did have to make some tweaks since I have a few containers running on ports that conflict with this, but other than one small change to the port and setting the invidious network mode to bridge, it spun up and my videos started working again.

 

Thanks for sharing this.

I've gotten the webUI for Invidious up using the CA release as per this thread. However, I had to comment out the "Configuration for using a HTTP proxy" or the container will never work. Doesn't get the IP address I set, can't view logs, nothing. Logs also had to be enabled in the config file.

 

 

Thanks to everyone who has contributed to this solution, and especially to @HuSoS for all of the detail. I used the info in your post but took a different route, since my dockers all have unique IP addresses on a custom network and I wanted to use Unraid's GUI rather than the compose plugin. Here's the write-up:

1. Follow these steps from HuSoS's post above, replacing the internal IP address for signature_server in Step 6 with the custom address I would be assigning to the helper:

   Quote

   Step 1. Stop Invidious container

    

   Step 2. You need to generate 2 value (visitor_data and po_token) from a computer or server that use the same IP as your Invidious instance.
   
   In Unraid you can open a terminal and run command below - In the log you'll see both value (Keep it for later)

   docker run quay.io/invidious/youtube-trusted-session-generator 

    

   Step 5. We need to truncate our "video table" in the database it's can be done with adminer or in command.

   https://github.com/iv-org/invidious/issues/4947#issuecomment-2373119661

    

   Step 6. Modify config.yml file in invidious folder, add and fill these 3 values from our previous step.

   signature_server:  [DOCKER-INTERNAL-IP-EX;172.17.0.17]:12999
   visitor_data: key (from step 2)
   po_token: token (from step 2)

    

2. Create a new container for the helper via the GUI:
   1. Docker > Add Container
   2. Switch to Advanced View
   3. Populate the following field values (icon is borrowed from Invidious docker, and optional):

      Name:				inv-sig-helper
      Repository:			quay.io/invidious/inv-sig-helper
      Icon URL:			https://raw.githubusercontent.com/Joshndroid/joshndroid-unraid-docker-templates/main/icons/invidious.png
      Post Arguments:			--tcp 0.0.0.0:12999
      Network Type:			[YOUR CHOSEN NETWORK | e.g.- Custom : br0]
      Fixed IP address (optional):	[STATIC IP ADDRESS | e.g. - 10.0.1.111]

       

   4. Add another Path, Port, Variable, Label or Device

      Config Type:	Variable
      Name:		RUST_LOG
      Key:		RUST_LOG
      Value:		info

   5. Done
3. Verify that the inv-sig-helper docker has successfully started (last line in the log should end with "Successfully fetched player")
4. Start the invidious container, verify that the logs show no errors, and enjoy!

Hello guys, first of all, thank you very much for the tutorial, I've been thinking for months that I had broken my invidious, I didn't know about YouTube blocking it. But even doing the stack by the portainer with docker compose and doing it manually by the unraid. I can register the user but I can't log in.

I thought it could be the database, I deleted it and started it again and nothing. I can't log in

Hi @erikmanzato , can you explain more context/details/error logs of your invidious instance?

 

When you try to login are you on local IP over HTTP or is your invidious instance on HTTPS? 
In my case I can only login over HTTPS(reverse proxy) but when I try INVIDIOUS:PORT over HTTP it's not working.
HTTP is by default insecure so i suspect it's somewhere in config file you can change something.

 

 

unraid config

Quote

 

appdata/invidious/config/config.yml
appdata/invidious/postgesql14

db:
  user: kemal
  password: kemal
  host: 192.168.0.200
  port: 5432
  dbname: invidious
check_tables: true
signature_server: 192.168.0.200:12999
port: 3000
domain: invidious.domain.xyz
https_only: true
po_token:xxxxx
visitor_data:xxxxx
popular_enabled: false
statistics_enabled: true
registration_enabled: true
login_enabled: true
captcha_enabled: true

LOG

- inv-sig-helper
[2025-01-10T06:53:54Z INFO  inv_sig_helper_rust] Successfully fetched player

- postgresql14
PostgreSQL Database directory appears to contain a database; Skipping initialization

- invidious
2025-01-10 16:08:27 UTC [info] 200 GET / 128.43µs
2025-01-10 16:08:28 UTC [info] 200 GET / 124.07µs
2025-01-10 16:08:28 UTC [info] 200 GET / 132.04µs
2025-01-10 16:08:28 UTC [info] 200 GET / 118.27µs
2025-01-10 16:08:29 UTC [info] 200 GET / 122.72µs
2025-01-10 16:08:29 UTC [info] 200 GET / 114.59µs
2025-01-10 16:08:44 UTC [info] 200 GET /search 618.62ms
2025-01-10 16:08:44 UTC [info] 200 GET /css/search.css 90.24µs
2025-01-10 16:08:44 UTC [info] 200 GET /js/watched_indicator.js 29.24µs
2025-01-10 16:08:45 UTC [info] ytimg_pool: Creating a new HTTP pool for "https://i.ytimg.com"
2025-01-10 16:08:45 UTC [info] 200 GET /ggpht/SLBk_zBM2dQJIt4YIzK6kMi2I3xyvSpDnxa6cQTcLzdeMRc4jQC8WYp8c71Tq-YweLcOr67A2IQ=s176-c-k-c0x00ffffff-no-rj-mo 247.67ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/YbugpcDHaPo/mqdefault.jpg 225.2ms
2025-01-10 16:08:45 UTC [info] 200 GET /ggpht/Qpb76PK45aNUeBH9UzemuuA6GWNd6QAstFT-4d7Okn4d7WruWiQo9UvIK2yowWdHCV3mRa9kpg=s176-c-k-c0x00ffffff-no-rj-mo 204.79ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/kwRU-okj37w/hqdefault.jpg 180.51ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/QrjzW6_jEYc/hqdefault.jpg 66.25ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/zskFbzsZu8s/hqdefault.jpg 195.93ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/vOZAWr8qS-M/hqdefault.jpg 37.12ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/b3CLdsLpPxI/mqdefault.jpg 42.11ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/cYu-ixXp604/mqdefault.jpg 137.36ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/0cmO8T40tPk/hqdefault.jpg 150.69ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/QzdbB6YnDEA/mqdefault.jpg 29.27ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/psOrRNt8jKw/mqdefault.jpg 32.06ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/54KnPTJLrHc/mqdefault.jpg 29.97ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/ucn8W2VEsJw/mqdefault.jpg 21.97ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/ntbpIfS44Gw/mqdefault.jpg 33.47ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/CEIaAKwO0tc/mqdefault.jpg 31.08ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/0cmO8T40tPk/mqdefault.jpg 24.42ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/0O4QdPRTtDg/hqdefault.jpg 383.88ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/0M9UH3g-XG8/mqdefault.jpg 242.65ms
2025-01-10 16:08:45 UTC [info] 200 GET /vi/twBqoCl1Pw0/mqdefault.jpg 264.71ms

 

 

portainer config

Quote

 

Portainer

version: "3"
services:

  invidious:
    image: quay.io/invidious/invidious:latest

    # image: quay.io/invidious/invidious:latest-arm64 # ARM64/AArch64 devices
    restart: unless-stopped
    ports:
      - "3000:3000"
    environment:
      # Please read the following file for a comprehensive list of all available
      # configuration options and their associated syntax:
      # https://github.com/iv-org/invidious/blob/master/config/config.example.yml
      INVIDIOUS_CONFIG: |
        db:
          dbname: invidious
          user: kemal
          password: kemal
          host: invidious-db
          port: 5432
        check_tables: true
        signature_server: inv_sig_helper:12999
        visitor_data: xxxxx
        po_token: xxxxx
        # external_port:
        domain: invidious.domain.xyz
        https_only: true
        # statistics_enabled: false
        hmac_key: xxxxx

    healthcheck:
      test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/trending || exit 1
      interval: 30s
      timeout: 5s
      retries: 2
    logging:
      options:
        max-size: "1G"
        max-file: "4"
    depends_on:
      - invidious-db

  inv_sig_helper:
    image: quay.io/invidious/inv-sig-helper:latest
    init: true
    command: ["--tcp", "0.0.0.0:12999"]
    environment:
      - RUST_LOG=info
    restart: unless-stopped
    cap_drop:
      - ALL
    read_only: true
    security_opt:
      - no-new-privileges:true

  invidious-db:
    image: docker.io/library/postgres:14
    restart: unless-stopped
    volumes:
      - postgresdata:/var/lib/postgresql/data
      - ./config/sql:/config/sql
      - ./docker/init-invidious-db.sh:/docker-entrypoint-initdb.d/init-invidious-db.sh
    environment:
      POSTGRES_DB: invidious
      POSTGRES_USER: kemal
      POSTGRES_PASSWORD: kemal
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"]

volumes:
  postgresdata:

 

 

in the db folder are the files of this image

appdata/invidious/postgesql14

 

It looks like an error in the preferences

Even though I have an account, I can't make changes

 

Quote

Title: `Index out of bounds (IndexError)` Date: `2025-01-15T01:05:41Z` Route: `/preferences?referer=%2F` Version: `2024.11.10-5d2dd40 @ (HEAD detached at v2.20241110.0)` <details> <summary>Backtrace</summary> <p> ``` Index out of bounds (IndexError) from src/invidious/routes/preferences.cr:185:8 in 'update' from lib/kemal/src/kemal/route.cr:12:9 in '->' from src/invidious/helpers/handlers.cr:30:37 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next' from lib/kemal/src/kemal/filter_handler.cr:21:7 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next' from src/invidious/helpers/handlers.cr:94:12 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next' from src/ext/kemal_static_file_handler.cr:112:11 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call' from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call' from /usr/share/crystal/src/http/server/request_processor.cr:51:11 in 'handle_client' from /usr/share/crystal/src/fiber.cr:143:11 in 'run' from ??? ``` </p> </details>