@graf I just saw an error message on tv.poast.org that I saw when I migrated FBXL video to peertube 5.0 about oauth failing. There are two things I needed to change to get it working properly.
First I needed to add the secrets part to my config file:
# Secrets you need to generate the first time you run PeerTube
secrets:
# Generate one using `openssl rand -hex 32`
peertube: '' # where there's a big series of letters and numbers in there
Second, my config was set to look at port 9000:
# Correspond to your reverse proxy server_name/listen configuration (i.e., your public PeerTube instance URL)
webserver:
https: false
hostname: 'localhost'
port: 9000
I needed to change the 9000 to 443 since it was on https externally and it looks like peertube 5 actually cares about that.
I might be totally off, but figure I'd pass what I learned on, maybe it'll help.
First I needed to add the secrets part to my config file:
# Secrets you need to generate the first time you run PeerTube
secrets:
# Generate one using `openssl rand -hex 32`
peertube: '' # where there's a big series of letters and numbers in there
Second, my config was set to look at port 9000:
# Correspond to your reverse proxy server_name/listen configuration (i.e., your public PeerTube instance URL)
webserver:
https: false
hostname: 'localhost'
port: 9000
I needed to change the 9000 to 443 since it was on https externally and it looks like peertube 5 actually cares about that.
I might be totally off, but figure I'd pass what I learned on, maybe it'll help.
Ah, it's just because I was using the old domain, the new domain doesn't have the same error.
nvm. (Maybe someone else with a peertube will see it and fix their stuff up)
nvm. (Maybe someone else with a peertube will see it and fix their stuff up)
- replies
- 1
- announces
- 0
- likes
- 1