mirror of
https://github.com/iv-org/invidious.git
synced 2025-04-20 07:35:53 -04:00
Update README.md
This commit is contained in:
parent
7212db6740
commit
46f5b62ecf
@ -131,7 +131,9 @@ It appears the working solution currently is to use:
|
||||
- po_token & visitor_data
|
||||
- a VPN proxy (privoxy, proton-privoxy, etc.)
|
||||
|
||||
I personally use proton VPN, you can get it along with your email here: https://pr.tn/ref/04PN5S3WMGBG - if you want VPN only you can try to get it there or just go to protonvpn.com. You can get a working proton-privoxy from https://github.com/catspeed-cc/proton-privoxy . I use one invidious instance, one sig helper, and one proton-privoxy per core. Each connection to nginx is routed to the least connected backend (currently I have 4) . I hope this is helpful to instance owners having troubles.
|
||||
I personally use proton VPN, you can get it along with your email here: https://pr.tn/ref/04PN5S3WMGBG - if you want VPN only you can try to get it there or just go to protonvpn.com. You can get a working proton-privoxy from https://github.com/catspeed-cc/proton-privoxy .
|
||||
|
||||
I use one invidious instance, one sig helper, and one proton-privoxy per core. Each connection to nginx is routed to the least connected backend (currently I have 4) . I hope this is helpful to instance owners having troubles.
|
||||
|
||||
|
||||
## inv_sig_helper notes
|
||||
|
Loading…
x
Reference in New Issue
Block a user