Should that be the recommended setup?
I think so, yeah (also for performance reasons and to have traefik reachable from IPv6)
Ok, so I just tested this and it works fine on a fresh VM, X-Forwarded-For is interpreted correctly, which means PEERTUBE_TRUST_PROXY
is read properly.
It must be that you're coming through…
Is the [...] passed actually as a list to the config file?
afaiu, it is passed as a string to the config file and it is then parsed as a json list further down. I'll try and debug it asap.
…
@3wordchant that's a very good idea, PR incoming :3
That is odd, trust_proxy
already contains the whole 10.0.0.0/8
block, see: https://git.autonomic.zone/coop-cloud/peertube/src/branch/main/compose.yml#L47
it looks like the…
Those files are served directly by nginx so they need to be in a named volume in order to be reachable.
What we could do instead as a workaround is use the nginx proxy-cache and forward the misses…
ok, so the issue is the cover image dimentions, libx264 can't work with odd sized frames... this is embarrassing, I should have noticed it.