-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
Describe the bug
I am running my invidous (using companion) instance on a small server in my flat. Connecting through local lan works and playback is fine. I am also using Tailscale as VPN so i can use invidous from work/train/whatever. This also works using the tailnet address.
I now added https routing to my tailnet in order to be able to log into invidous from my working place computer (if its is not using https the virus scanner raises a false alarm for "password stealer". it does so for everything not using https...).
I can, through https get into invidous, log in and see all the videos but playback silently fails. Neither the log for invidous or companion show anything out of the ordinary.
Steps to Reproduce
- Create a tailnet with http routing. In my case https://invidous.sometailnet.ts:10000 -> http://localserver:3001
- Click on 'any video
- No playback possible
Additional context
Server is running DietPi with a recently updated docker based installation of invidous and companion.
Server LAN IP: 10.0.0.2
Server Tailscale IP: 100.64.0.2
HTTPS routing: https://invidous.sometailnet.ts:10000 -> 100.64.0.2:3001
HTTPS routing: https://invidous.sometailnet.ts:10002 -> 100.64.0.2:8282
Excerp from the docker file:
invidious:
image: quay.io/invidious/invidious:master
restart: unless-stopped
ports:
- "3001:3000"
environment:
INVIDIOUS_CONFIG: |
db:
dbname: invidious
user: kemal
password: kemal
host: invidious-db
port: 5432
check_tables: true
invidious_companion:
- private_url: "http://companion:8282"
public_url: "https://invidous.sometailnet.ts:10002"
invidious_companion_key: "123456789"
hmac_key: "123456789"
....
I suppose it has to do with my public url.. but i am not sure here. changing it to the tailnet address didnt help me ...
Any ideas? Or could this be actually a bug...