HuSoS

Hi@Armadageddon , "The project root in the Docker container is now /app. You have to adjust the volume mapping of the .env file in the compose.yaml file: ./.env:/app/.env." You need to edit "(.env) File" section and change Container Path: /var/www/html/.env to /app/.env if i'm not wrong that it

My original post to use inv-sig-helper with Invidious which require visitor_data and po_token. This method is still available but less private because YT can still track from the token which video is played. So we can now use invidious-companion which generate new po_token at intervals so it's more private (main goal of invidious). Here's how you can achieve this. Step 1. Stop Invidious container Step 2. Generate HMAC_KEY with cmd pwgen 16 1 or openssl rand -hex 8 Step 2a. Create a folder in your invidious appdata or where you want.. Something like /mnt/user/appdata/invidious/{YOURFOLDER}/ Make sure you can write and read this folder. Step 2b. Create new container in Unraid Docker section Expand Create a new container for the helper via the GUI: Docker > Add Container Switch to Advanced View Populate the following field values (icon is borrowed from Invidious docker, and optional): Name: invidious-companion Repository: quay.io/invidious/invidious-companion:latest Icon URL: Network Type: [YOUR CHOSEN NETWORK | e.g.- Custom : br0] Fixed IP address (optional): [STATIC IP ADDRESS | e.g. - 10.0.1.111] Add another Variable: Name: SERVER_SECRET_KEY Key: SERVER_SECRET_KEY Default & Value: Step 2 (HMAC_KEY) Optionnal (Password Mask) : Yes Add another Path: Name & Container path : /var/tmp/youtubei.js/Config Host Path & Default Value : /mnt/user/appdata/invidious/{YOURFOLDER}/ Optionnal (It's run on port 8282 so you can change it if needed) Add another Port : Name: Port Container Port: 8282 Host Port: 8282 (Change this value if you need) Default Value: 8282 Connection Type : TCP -> Apply (Start) invidious compagnion and you should get logs like Step 3. Invidious - config.yml If you have signature_server, visitor_data and po_token from inv-sig-helper in your file delete or comment them with # in front. Add this code somewhere in config.yml invidious_companion: # URL used for the internal communication between invidious and invidious companion - private_url: "http://{Companion-IP}:8282" # (public) URL used for the communication between your browser and invidious companion # IF you are using a reverse proxy OR accessing invidious from an external IP then you NEED to change this value # Please consult for more doc: https://github.com/unixfox/invidious/blob/invidious-companion/config/config.example.yml#L57-L88 - public_url: "http://{Companion-IP}:8282" # IT is NOT recommended to use the same key as HMAC KEY. Generate a new key! invidious_companion_key: "{HMAC_KEY}" This is pretty much it... save config.yml then run invidious container. If you run invidious behind reverse proxy you may look at official docs if you have problems Caddy, Nginx etc.. Invidious-Companion with NGINX - https://docs.invidious.io/companion-nginx/ Official documentation : https://docs.invidious.io/companion-installation/ 2025/09/14 - EDIT : MIGRATION NEEDED (NEW): Invidious companion Invidious companion replace both inv-sig-helper and youtube-trusted-session-generator. You don't need to execute youtube-trusted-session-generator anymore. WHAT NEED TO BE DONE FOR THIS MIGRATION EDIT CONFIG.yml file 1. SOULD BE -> - private_url: "http://{Companion-IP}:8282/companion" "/companion" added 2. -public_url (Not required anymore)

Hi, I had this problem and I was able to fixed it, I'm running plex bylscr.io/linuxserver on Unraid. First of all back-up you Plex Database in case and then... (com.plexapp.plugins.library.blobs.db and com.plexapp.plugins.library.db) Located - /Plex Media Server/Plug-in Support/Databases With DB Browser for SQLITE https://sqlitebrowser.org/ When need to make some modification in DB file named - com.plexapp.plugins.library.db Go to Browse Data in the DB Table media_stream_settings you will see some entries so delete them all. (Exemple this image) After that just save your file. Because you've made some changes, your DB gonna have some errors if you try to run plex. You'll need to fix-it use this tool. https://github.com/ChuckPa/PlexDBRepair Download - DBRepair.sh in your plex appdata folder. Open console while clicking on Plex icon in docker section. Navigate to you DBRepair.sh then run ./DBRepair.sh Press 1. To be sure PMS is stopped Press 2. for 'automatic' repair. (Wait) Press 7. To start PMS again Then now all good... back to normal. Hope you can fix-it.

@erikmanzato The error you got on last post its not related to account seems a bug from invidious - Maybe related to https://github.com/iv-org/invidious/issues/3659 Do you have imported a list of channel from youtube?

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.

Hi @Mainfrezzer, I've installed panel but got some error with wings. INFO: [Dec 25 09:45:21.998] creating missing pelican0 interface, this could take a few seconds... FATAL: [Dec 25 09:45:21.998] failed to configure docker environment error=Error response from daemon: invalid pool request: Pool overlaps with other one on this address space I don't have Pterodactyl installed and no Pterodactyl network on my docker from previous installation (1 year ago). Do you have an idea how to bypass this problem since with your last version you added "Dockernetwork - The IP Ranges, it shouldnt collide with Pterodactyl created networks. Networkname is pelican_net with "172.18.99.0/24" and "fdba:17d8:6c94::/64""

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

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

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.

@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..