You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When browsing to our dev instance of PeerTube at https://dev.wtfayla.com:16643, we get the oft-occurring error message in the bottom right of the browser window stating the following:
Error Cannot retrieve OAuth Client credentials: Getting client tokens for host dev.wtfayla.com is forbidden. Ensure you have correctly configured PeerTube (config/ directory), in particular the "webserver" section.
This also appears in journalctl (see attached).
Running Peertube and NGINX on a Ubuntu 22.04 server. Server has two NICs:
WAN-facing: 50.75.172.138 (dev.wtfayla.com)
LAN-facing: 192.168.1.166
NGINX is bound to 50.75.172.138 on TCP port 16643
We've seen many posts regarding this, but we think we've atomized it a bit more. We have two scenarios:
Describe the current behavior
When browsing to our dev instance of PeerTube at https://dev.wtfayla.com:16643, we get the oft-occurring error message in the bottom right of the browser window stating the following:
Error Cannot retrieve OAuth Client credentials: Getting client tokens for host dev.wtfayla.com is forbidden. Ensure you have correctly configured PeerTube (config/ directory), in particular the "webserver" section.
This also appears in journalctl (see attached).
Running Peertube and NGINX on a Ubuntu 22.04 server. Server has two NICs:
NGINX is bound to 50.75.172.138 on TCP port 16643
We've seen many posts regarding this, but we think we've atomized it a bit more. We have two scenarios:
FIRST SCENARIO:
`listen:
hostname: '127.0.0.1'
port: 9000
https: true
hostname: 'dev.wtfayla.com'
port: 16643`
Browse to https://dev.wtfayla.com:16643: ERROR
SECOND SCENARIO:
`listen:
hostname: '192.168.1.166'
port: 9000
https: false
hostname: '192.168.1.166'
port: 9000`
Browse to http://192.168.1.166:9000 (from LAN): NO ERROR
Steps to reproduce
Describe the expected behavior
Additional information
PeerTube instance:
Browser name, version and platforms on which you could reproduce the bug: Windows/Brave/1.73.105 Chromium: 131.0.6778.265 (Official Build) (64-bit)], [MacOS/Firefox/134], [MacOS/Chrome/131]
Link to browser console log if relevant:
Link to server log if relevant (
journalctl
or/var/www/peertube/storage/logs/
):journalctl.txt
peertube.conf.txt
production.yaml.txt
The text was updated successfully, but these errors were encountered: