Comparar commits
1 Commits
| Autor | SHA1 | Data | |
|---|---|---|---|
 Émilien (perso)
|
1fa4d8b23d |
@@ -28,7 +28,7 @@ Lists of third-party projects that use or support Invidious.
|
||||
| [Redirector](https://github.com/einaregilsson/Redirector) | Extension for Firefox and Chromium that can manually be configured to process Invidious Redirects. For details, see the [setup page](./redirector.md) to use it with Invidious. | [Source](https://github.com/einaregilsson/Redirector) / [Firefox](https://addons.mozilla.org/addon/redirector) / [Chrome](https://chrome.google.com/webstore/detail/redirector/ocgpenflpmgnfapjedencafcfakcekcd) |
|
||||
| [Invidious Copy URL](https://github.com/recette-lemon/invidious-copy-url) | Adds context menu options on Invidious to copy shortened YouTube URL at current time or not (Requires using developer mode in Chrome or a developer version of Firefox). | |
|
||||
| [Privacy Redirect](https://github.com/SimonBrazell/privacy-redirect) | Redirects YouTube to Invidious, Twitter to Nitter, and Instagram to Bibliogram. | [Source](https://github.com/SimonBrazell/privacy-redirect) / [Firefox](https://addons.mozilla.org/addon/privacy-redirect) / [Chrome](https://chrome.google.com/webstore/detail/privacy-redirect/pmcmeagblkinmogikoikkdjiligflglb) |
|
||||
| [SponsorBlock](https://github.com/ajayyy/SponsorBlock) | A crowd-sourced extension to skip sponsorships. Support Invidious instances if enabled in the options. | [Source](https://github.com/ajayyy/SponsorBlock) / [Firefox](https://addons.mozilla.org/addon/sponsorblock) / [Chrome](https://chrome.google.com/webstore/detail/mnjggcdmjocbbbhaepdhchncahnbgone) |
|
||||
| [SponsorBlock](https://github.com/ajayyy/SponsorBlock) | A crowd-sourced extension to skip sponsorships. Support invidious instances if enabled in the options. | [Source](https://github.com/ajayyy/SponsorBlock) / [Firefox](https://addons.mozilla.org/addon/sponsorblock) / [Chrome](https://chrome.google.com/webstore/detail/mnjggcdmjocbbbhaepdhchncahnbgone) |
|
||||
| [Inviduration](https://github.com/rsapkf/inviduration) | Firefox extension that shows total duration of playlists on Invidious. | [Source](https://github.com/rsapkf/inviduration) / [Firefox](https://addons.mozilla.org/addon/inviduration) |
|
||||
| [Alter](https://github.com/w3bdev1/alter) | Firefox extension that redirects YouTube, Twitter and Reddit to Invidious, Nitter and Teddit respectively. | [Source](https://github.com/w3bdev1/alter) / [Firefox](https://addons.mozilla.org/addon/alter) |
|
||||
|
||||
@@ -52,7 +52,6 @@ Lists of third-party projects that use or support Invidious.
|
||||
| [FreshRSS Extension](https://github.com/tmiland/freshrss-invidious) | A FreshRSS extension to directly embed videos from Invidious channel feeds. | |
|
||||
| [UntrackMe](https://f-droid.org/en/packages/app.fedilab.nitterizeme) | Android app to rewrite YouTube links to Invidious. Can optionally play videos in the app as well. | |
|
||||
| [Kodi add-on](https://github.com/lekma/plugin.video.invidious) | Watch YouTube videos in the Kodi media center, using the Invidious API. Privacy-friendly alternative to the YouTube API add-on. | |
|
||||
| [Koutube](https://github.com/iGerman00/koutube) | Watch YouTube videos on Discord without loading the YouTube embed. Quickly replace any YouTube links using the sed syntax (s/y/k) or by swapping the <kbd>y</kbd> with a <kbd>k</kbd>. | [Source](https://github.com/iGerman00/koutube) / [Website](https://koutube.com) |
|
||||
|
||||
### Utilities
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ sudo dnf install podman
|
||||
### Download the configuration files from Invidious' repository
|
||||
|
||||
Note: Currently the repository has to be cloned, this is because the `init-invidious-db.sh` file and the `config/sql` directory have to be mounted to the postgres container (See the volumes section in the postgres' container). This "problem" will be solved in the future.
|
||||
> `<INV-PATH>` Absolute path in your home directory where Invidious will be downloaded (e.i. /home/johnsmith/.inv)
|
||||
> `<INV-PATH>` Absolute path in your home directory where invidious will be downloaded (e.i. /home/johnsmith/.inv)
|
||||
|
||||
```bash
|
||||
cd <INV-PATH>
|
||||
@@ -99,113 +99,3 @@ loginctl enable-linger
|
||||
podman auto-update
|
||||
podman image prune -f
|
||||
```
|
||||
|
||||
## Podman via systemd
|
||||
|
||||
This method is suitable for systems which come with Podman version 5.x or higher and systemd (e.g. Fedora, CentOS Stream 9 or clones). Instructions are written for root-less mode, do not run the commands as root since paths are different. Ensure that SELinux is in enforcing mode for maximum security.
|
||||
|
||||
Create a new volume for database:
|
||||
|
||||
podman volume create invidious-db
|
||||
|
||||
Start a temporary container:
|
||||
|
||||
podman run --rm -it --name invidious-init -v invidious-db:/var/lib/postgresql/data:Z -p 5432:5432 -e POSTGRES_DB=invidious -e POSTGRES_USER=kemal -e POSTGRES_PASSWORD=kemal docker.io/library/postgres:14
|
||||
|
||||
In another terminal, migrate the database:
|
||||
|
||||
export PGPASSWORD=kemal
|
||||
for F in channels videos channel_videos users session_ids nonces annotations playlists playlist_videos; do
|
||||
curl -s https://raw.githubusercontent.com/iv-org/invidious/refs/heads/master/config/sql/$F.sql | \
|
||||
psql -h localhost -p 5432 -U kemal invidious
|
||||
done
|
||||
|
||||
Shutdown the temporary container, it is no longer needed. Create a database volume unit:
|
||||
|
||||
cat > ~/.config/containers/systemd/invidious-db.volume <<EOF
|
||||
[Volume]
|
||||
VolumeName=invidious-db
|
||||
EOF
|
||||
|
||||
And a database container:
|
||||
|
||||
cat > ~/.config/containers/systemd/invidious-db.container <<EOF
|
||||
[Container]
|
||||
ContainerName=invidious-db
|
||||
Environment=POSTGRES_DB=invidious POSTGRES_USER=kemal POSTGRES_PASSWORD=kemal
|
||||
Image=docker.io/library/postgres:14
|
||||
HealthCmd=pg_isready -h localhost -p 5432 -U kemal -d invidious
|
||||
Notify=healthy
|
||||
Pod=invidious.pod
|
||||
Volume=invidious-db.volume:/var/lib/postgresql/data:Z
|
||||
EOF
|
||||
|
||||
Create a helper container:
|
||||
|
||||
cat > ~/.config/containers/systemd/invidious-sig-helper.container <<EOF
|
||||
[Container]
|
||||
ContainerName=invidious-sig-helper
|
||||
Environment=RUST_LOG=info
|
||||
Image=quay.io/invidious/inv-sig-helper:latest
|
||||
Exec=--tcp 0.0.0.0:12999
|
||||
Pod=invidious.pod
|
||||
EOF
|
||||
|
||||
Generate your `VISITOR_DATA` an `PO_TOKEN` secrets. For more information about these, read the information dialog above.
|
||||
|
||||
podman run quay.io/invidious/youtube-trusted-session-generator
|
||||
|
||||
Set those secrets as temporary environmental variables, also generate a random string for HMAC secret:
|
||||
|
||||
HMAC=$(openssl rand -base64 21)
|
||||
VISITOR_DATA="ABCDEF%3D%3D" # notsecret
|
||||
PO_TOKEN="MpOIfiljfsdljds-Lljfsdk-ojrdjXVs==" # notsecret
|
||||
|
||||
In the same terminal where you defined the environmental variables, create new environmental config file:
|
||||
|
||||
cat > ~/.config/containers/systemd/invidious.env <<EOF
|
||||
INVIDIOUS_DATABASE_URL="postgres://kemal:kemal@invidious-db:5432/invidious"
|
||||
#INVIDIOUS_CHECK_TABLES=true
|
||||
#INVIDIOUS_DOMAIN="inv.example.com"
|
||||
INVIDIOUS_SIGNATURE_SERVER="invidious-sig-helper:12999"
|
||||
INVIDIOUS_VISITOR_DATA="$VISITOR_DATA"
|
||||
INVIDIOUS_PO_TOKEN="$PO_TOKEN"
|
||||
INVIDIOUS_HMAC_KEY="$HMAC"
|
||||
EOF
|
||||
|
||||
From now on, if you need to change configuration just edit the generated file `~/.config/containers/systemd/invidious.env`. Now, create Invidious container unit:
|
||||
|
||||
cat > ~/.config/containers/systemd/invidious.container <<EOF
|
||||
[Container]
|
||||
ContainerName=invidious
|
||||
EnvironmentFile=%h/.config/containers/systemd/invidious.env
|
||||
Image=quay.io/invidious/invidious:latest
|
||||
Pod=invidious.pod
|
||||
[Unit]
|
||||
After=invidious-db.service
|
||||
EOF
|
||||
|
||||
And finally, create pod unit. Note only port 3000 is exposed, do not expose other ports!
|
||||
|
||||
cat > ~/.config/containers/systemd/invidious.pod <<EOF
|
||||
[Pod]
|
||||
PodName=invidious
|
||||
PublishPort=3000:3000
|
||||
[Install]
|
||||
WantedBy=multi-user.target default.target
|
||||
EOF
|
||||
|
||||
Systemd units are generated on-the-fly during `daemon-reload` command, but before that let's check syntax with quadlet generator. Note, you need Podman version 5.0 or higher, older versions will not work:
|
||||
|
||||
/usr/libexec/podman/quadlet -dryrun -user
|
||||
|
||||
Reload systemd daemon. Keep in mind you need to do this command every time you change a unit file, you can change the environmental file freely tho.
|
||||
|
||||
systemctl --user daemon-reload
|
||||
|
||||
And the whole application can be now started:
|
||||
|
||||
systemctl --user start invidious-pod
|
||||
|
||||
Keep in mind that generated units cannot be enabled using `systemctl enable`, the main pod will be enabled automatically. If you do not like this behavior, remove the `WantedBy` line from `invidious.pod`.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Configuration
|
||||
|
||||
An comprehensive list of all the available config options, with detailed explaination and default values is available under [`config/config.example.yml`](https://github.com/iv-org/invidious/blob/master/config/config.example.yml) in the main Invidious repository.
|
||||
An comprehensive list of all the available config options, with detailed explaination and default values is available under [`config/config.example.yml`](https://github.com/iv-org/invidious/blob/master/config/config.example.yml) in the main invidious repository.
|
||||
|
||||
The path to the configuration file can be overridden with the
|
||||
`INVIDIOUS_CONFIG_FILE` environment variable.
|
||||
|
||||
@@ -1,75 +0,0 @@
|
||||
# How to make a new Invidious release
|
||||
|
||||
## Preamble
|
||||
|
||||
In the following document, `vX.Y.Z` is the release version, which should follow
|
||||
the pattern `v<MAJOR>.<YYYY><MM><DD>.<PATCH>`
|
||||
|
||||
The major component is only updated on breaking changes (database migrations,
|
||||
incompatible config changes). The minor component is the current UTC date.
|
||||
The patch component is updated if a second release is done the same day.
|
||||
|
||||
|
||||
## Step 0
|
||||
|
||||
Make sure you're synced with upstream:
|
||||
```sh
|
||||
git checkout master
|
||||
git remote update
|
||||
git pull origin master
|
||||
```
|
||||
|
||||
|
||||
## Step 1
|
||||
|
||||
Update CHANGELOG.md to reflect the changes made since the last release.
|
||||
|
||||
Each changelog entry is composed of a summary and a list of PRs (~= diff).
|
||||
|
||||
The summary should be simple and concise, and only reflect most important
|
||||
changes, preferably sorted by impact (new features/breaking changes that the
|
||||
users will see goes first, changes that affect developers/API users should go
|
||||
last). Minor changes that are related to repo maintenance can be ignored.
|
||||
|
||||
Do not forget to list **ALL** the PRs that have been merged since the last
|
||||
release, with the proper links.
|
||||
|
||||
Note: Maybe this should be done each time a PR is marged?
|
||||
|
||||
|
||||
## Step 2
|
||||
|
||||
Commit the changes made to `CHANGELOG.md`:
|
||||
```sh
|
||||
git commit -S -m "Release vX.Y.Z"
|
||||
```
|
||||
|
||||
**THEN** tag your release, like so:
|
||||
```sh
|
||||
git tag -as vX.Y.Z
|
||||
```
|
||||
|
||||
Git will ask to provide a tag message. All you have to do is copy/pasting the
|
||||
summary from `CHANGEMLOG.md` and adapt a the formatting as required. Do not
|
||||
include the list of PRs merged.
|
||||
|
||||
|
||||
## Step 3
|
||||
|
||||
Once you have checked everything, push to GitHub:
|
||||
```sh
|
||||
git push origin master
|
||||
git push upstream vX.Y.Z
|
||||
```
|
||||
|
||||
|
||||
## Step 4
|
||||
|
||||
Got to GitHub to make a new release:
|
||||
https://github.com/iv-org/invidious/releases/new
|
||||
|
||||
Select the tag your previously created, leave `target` set to `master`,
|
||||
and then copy paste the text you wrote to `CHANGELOG.md` (both the summary and
|
||||
the list of PRs merged since last release).
|
||||
|
||||
And then click "publish"!
|
||||
+2
-5
@@ -118,7 +118,7 @@ or delete these data at any time from your user account page.
|
||||
## **Q:** What data is shared with YouTube?
|
||||
|
||||
**A:** By default, the video stream is fetched directly from Google's servers
|
||||
(`googlevideo.com`) in order to reduce the bandwidth required by Invidious,
|
||||
(`googlevideo.com`) in order to reduce the bandwidth required by invidious,
|
||||
meaning that Google will be able to see your IP address and some other data
|
||||
commonly sent by web browsers, like your user-agent string.
|
||||
|
||||
@@ -137,9 +137,6 @@ sent by your browser.
|
||||
|
||||
**A:** This problem can occur in different scenarios:
|
||||
|
||||
* If you are the one that have installed Invidious, please read the page
|
||||
["All the YouTube error messages explained with solutions"](/youtube-errors-explained/)
|
||||
|
||||
* If you're trying to watch a music clip, Youtube is likely blocking the
|
||||
video stream. Try enabling `Proxy videos` in the preferences (or add
|
||||
`&local=1` in the URL). Switching to another instance is also a good
|
||||
@@ -253,7 +250,7 @@ used for the session (`SID`) and preferences (`PREFS`) cookies. If set
|
||||
incorrectly, the cookies will be invalid, and your browser will silently
|
||||
ignore them.
|
||||
|
||||
**If you access your Invidious instance by IP address (like `192.168.1.205`)
|
||||
**If you access your invidious instance by IP address (like `192.168.1.205`)
|
||||
then leave the `domain` config option EMPTY!**
|
||||
|
||||
Common invalid values include:
|
||||
|
||||
@@ -12,7 +12,7 @@ This proxy server will only redirect the [TCP](https://en.wikipedia.org/wiki/Tra
|
||||
|
||||
By forwarding the actual HTTP protocol this is more compute intensive and won't be covered in this tutorial.
|
||||
|
||||
You need to proxy the HTTP protocol normally like you would already do with your current web server for Invidious. But in this case from the proxy server to your existing infrastructure. Then also setup the certificates for HTTPS.
|
||||
You need to proxy the HTTP protocol normally like you would already do with your current web server for invidious. But in this case from the proxy server to your existing infrastructure. Then also setup the certificates for HTTPS.
|
||||
|
||||
Then you optionally preserve the IP address of your clients using for example on NGINX set_real_ip_from and real_ip_header.
|
||||
|
||||
|
||||
+1
-1
@@ -19,7 +19,6 @@
|
||||
|
||||
- [Installation](./installation.md)
|
||||
- [Configuration](./configuration.md)
|
||||
- [YouTube error messages explained with solutions](./youtube-errors-explained.md)
|
||||
- [NGINX reverse proxy setup](./nginx.md)
|
||||
- [Caddy reverse proxy setup](./caddy.md)
|
||||
- [Apache2 reverse proxy setup](./apache2.md)
|
||||
@@ -28,6 +27,7 @@
|
||||
- [Registering users manually](./register-user.md)
|
||||
- [Reset user password](./reset-password.md)
|
||||
- [Known Exception in log](./known-exception.md)
|
||||
- [Make Invidious requests data from YouTube through a VPN using Gluetun (in case your IP is blocked)](./gluetun.md)
|
||||
|
||||
## For public instance Owners
|
||||
- [Handling takedown notices](./takedown.md)
|
||||
|
||||
@@ -341,9 +341,9 @@ Detailed configuration available in the [configuration guide](./configuration.md
|
||||
|
||||
You must set a random generated value for the parameter `hmac_key:`! On Linux you can generate it using the command `pwgen 20 1`.
|
||||
|
||||
Because of various issues, Invidious **must** be restarted often, at least once a day, ideally every hour.
|
||||
Because of various issues Invidious **must** be restarted often, at least once a day, ideally every hour.
|
||||
|
||||
If you use a reverse proxy, you **must** configure Invidious to properly serve request through it:
|
||||
If you use a reverse proxy, you **must** configure invidious to properly serve request through it:
|
||||
|
||||
`https_only: true` : if you are serving your instance via https, set it to true
|
||||
|
||||
@@ -353,7 +353,7 @@ If you use a reverse proxy, you **must** configure Invidious to properly serve r
|
||||
|
||||
`use_pubsub_feeds: true`: if you are serving your instance on the internet, allow for faster notification of new videos ([detailed explanation](https://github.com/iv-org/invidious/blob/97c4165f55c4574efb554c9dae8d919d08da1cdd/config/config.example.yml#L409)).
|
||||
|
||||
`use_innertube_for_captions: true`: if you are serving a public instance or you are hosting Invidious in a datacenter, allow to unblock captions ([detailed explanation](https://github.com/iv-org/invidious/issues/2567#issuecomment-1727928996)).
|
||||
`use_innertube_for_captions: true`: if you are serving a public instance or you are hosting invidious in a datacenter, allow to unblock captions ([detailed explanation](https://github.com/iv-org/invidious/issues/2567#issuecomment-1727928996)).
|
||||
|
||||
## Update Invidious
|
||||
|
||||
|
||||
+6
-2
@@ -10,14 +10,18 @@
|
||||
|
||||
* [inv.nadeko.net](https://inv.nadeko.net) 🇨🇱 - Source code/changes: https://git.nadeko.net/Fijxu/invidious - CAPTCHA: mCaptcha (https://mcaptcha.org/)
|
||||
|
||||
* [invidious.jing.rocks](https://invidious.jing.rocks) 🇯🇵 - Source code/changes: https://forgejo.jing.rocks/jing/invidious
|
||||
|
||||
* [invidious.nerdvpn.de](https://invidious.nerdvpn.de) 🇺🇦 - Source code/changes: https://github.com/Sommerwiesel/invidious-nerdvpn
|
||||
|
||||
* [invidious.jing.rocks](https://invidious.jing.rocks) 🇯🇵 - Source code/changes: https://forgejo.jing.rocks/jing/invidious
|
||||
|
||||
* [invidious.privacyredirect.com](https://invidious.privacyredirect.com) 🇫🇮
|
||||
|
||||
### Tor Onion Services:
|
||||
|
||||
* [inv.nadekonw7plitnjuawu6ytjsl7jlglk2t6pyq6eftptmiv3dvqndwvyd.onion](http://inv.nadekonw7plitnjuawu6ytjsl7jlglk2t6pyq6eftptmiv3dvqndwvyd.onion) 🇨🇱 (Onion of inv.nadeko.net)
|
||||
|
||||
* [nerdvpneaggggfdiurknszkbmhvjndks5z5k3g5yp4nhphflh3n3boad.onion](http://nerdvpneaggggfdiurknszkbmhvjndks5z5k3g5yp4nhphflh3n3boad.onion) 🇺🇦 (Onion of invidious.nerdvpn.de)
|
||||
|
||||
### I2P Eepsites:
|
||||
|
||||
* [zzlsbhhfvwg3oh36tcvx4r7n6jrw7zibvyvfxqlodcwn3mfrvzuq.b32.i2p](http://zzlsbhhfvwg3oh36tcvx4r7n6jrw7zibvyvfxqlodcwn3mfrvzuq.b32.i2p) 🇨🇱 (Eepsite of inv.nadeko.net)
|
||||
|
||||
@@ -78,7 +78,7 @@ If needed, IPv6 official documentation for Docker is at https://docs.docker.com/
|
||||
}
|
||||
```
|
||||
2. Restart Docker
|
||||
3. In your docker-compose file of Invidious. Add these lines at the end of your docker-compose
|
||||
3. In your docker-compose file of invidious. Add these lines at the end of your docker-compose
|
||||
```yaml
|
||||
networks:
|
||||
default:
|
||||
|
||||
@@ -49,7 +49,7 @@ For clarity, an example of a URL parameter would be &related_videos=false&commen
|
||||
|
||||
For redirects with ? in the URL, the Parameter string will start with &, while redirects without ? in the URL should have a Parameter string begining with ?, so https://[Invidious Domain Here]/$2 becomes ```https://[Invidious Domain Here]/$2?related_videos=false&comments=false```
|
||||
|
||||
Should you choose to use URL Parameters, I would reccomend adding the following rules to both ensure all Invidious videos load with your preference, and to ensure that unnecesary parameters are not added when already applied.
|
||||
Should you choose to use URL Parameters, I would reccomend adding the following rules to both ensure all invidious videos load with your preference, and to ensure that unnecesary parameters are not added when already applied.
|
||||
|
||||
# Rule 5 (Redirects Invidious Video URLs with parameters)
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Reset user password
|
||||
|
||||
Resetting a user's Invidious password needs you to edit the database.
|
||||
Resetting a user's invidious password needs you to edit the database.
|
||||
|
||||
Firstly, generate a bcrypt-encrypted hash for the new password you want to set for the user.
|
||||
|
||||
|
||||
@@ -1,49 +0,0 @@
|
||||
# All the YouTube error messages explained with solutions
|
||||
|
||||
**DISCLAIMER**: If you are just an user of a public instance. This documentation is not for you. Please instead redirect your Invidious instance maintainer to this page or switch to another public instance: [https://instances.invidious.io](https://instances.invidious.io)
|
||||
|
||||
## Error: non 200 status code. Youtube API returned status code 429
|
||||
|
||||
### Error explained
|
||||
|
||||
YouTube is limiting the traffic that you can sent to their servers. This error may appear for a duration of 24 hours.
|
||||
|
||||
### Cause(s)
|
||||
|
||||
Usually it is related to a lot of traffic being generated for refreshing your subscriptions.
|
||||
|
||||
- You have modified the parameter `channel_refresh_interval` and thus you are forcing the refresh of your subscriptions too quickly for YouTube.
|
||||
- You are subscribed to a lot of channels. YouTube may classify this as abuse due to Invidious having to check for new videos on a lot of channels.
|
||||
- You have sent a lot of traffic in another manner. Like by using the Invidious API.
|
||||
- Someone on your network is sending a lot of traffic to YouTube.
|
||||
|
||||
### Solution(s)
|
||||
|
||||
- Try to keep the `channel_refresh_interval` parameter commented to let Invidious refreshing your subscriptions less frequently.
|
||||
- Unsubscribe from some channels. While this may not be ideal, this will definitively send less data to YouTube.
|
||||
- Configure pubsub: [/installation/#post-install-configuration](/installation/#post-install-configuration). This requires your Invidious to be available on the internet and through a public domain.
|
||||
After this you can try to extend the refresh interval, like to `channel_refresh_interval: 240m`.
|
||||
You will still get almost instantaneous notifications from new YouTube videos thanks to pubsub but you will induce less refreshing traffic to YouTube servers. As pubsub is method for YouTube to notify your Invidious instance for new videos.
|
||||
- Change your public IP address. This may not solve the issue permanently but temporarily solve it.
|
||||
|
||||
## Sign in to confirm you are not a bot - This helps protect our community
|
||||
|
||||
### Error explained
|
||||
|
||||
YouTube is blocking the communication of Invidious to their servers.
|
||||
|
||||
### Cause(s)
|
||||
|
||||
- YouTube is running different mechanisms to detect the usage of non official YouTube clients. Your Invidious instance may have been detected by their system.
|
||||
- Your IP address is blacklisted from YouTube servers. It is known that YouTube block datacenter IP addresses.
|
||||
|
||||
### Solution(s)
|
||||
|
||||
First make sure that you are running the latest version of Invidious and you are using inv_sig_helper. Please see [the updated installation guide](/installation/).
|
||||
|
||||
After which you can try these solutions:
|
||||
|
||||
- Change your public IP address. Reboot your router or by configuring a proxy in Invidious: https://github.com/iv-org/invidious/blob/2150264d849771df8f15bab172ab6d87eeb80c55/config/config.example.yml#L176-L185
|
||||
- If you have IPv6 on the computer hosting Invidious, you can try to rotate your IPv6 public address, tutorial available here: "[Rotate your IPv6 address for escaping YouTube blocking](/ipv6-rotator/)"
|
||||
|
||||
All of these options do not guarantee you to bring back Invidious to working conditions. These are just advices for trying to unblock your Invidious instance from YouTube. Make sure to always specify any modification being done to your Invidious when reporting issues.
|
||||
+1
-1
@@ -24,7 +24,6 @@ nav:
|
||||
- 'For Administrators':
|
||||
- 'installation.md'
|
||||
- 'configuration.md'
|
||||
- 'youtube-errors-explained.md'
|
||||
- 'nginx.md'
|
||||
- 'caddy.md'
|
||||
- 'apache2.md'
|
||||
@@ -33,6 +32,7 @@ nav:
|
||||
- 'register-user.md'
|
||||
- 'reset-password.md'
|
||||
- 'known-exception.md'
|
||||
- 'gluetun.md'
|
||||
- 'For public instances Owners':
|
||||
- 'takedown.md'
|
||||
- 'hide-instance-behind-proxy-server.md'
|
||||
|
||||
Referência em uma Nova Issue
Bloquear um usuário