mirror of
https://github.com/mother-of-all-self-hosting/mash-playbook
synced 2024-11-10 06:14:17 +00:00
Upgrade PeerTube (v6.0.3-0 -> v6.0.3-4) and simplify reverse-proxy setup
This commit is contained in:
parent
f45a2cd58d
commit
9ac7a4ca15
2 changed files with 1 additions and 20 deletions
|
@ -211,22 +211,3 @@ You should then be able to log in with:
|
|||
|
||||
- username: `root`
|
||||
- password: the password you've set in `peertube_config_root_user_initial_password` in `vars.yml`
|
||||
|
||||
|
||||
## Adjusting the trusted reverse-proxy networks
|
||||
|
||||
If you go to **Administration** -> **System** -> **Debug** (`/admin/system/debug`), you'll notice that PeerTube reports some local IP instead of your own IP address.
|
||||
|
||||
To fix this, you need to adjust the "trusted proxies" configuration setting.
|
||||
|
||||
The default installation uses a Traefik reverse-proxy, so we suggest that you make PeerTube trust the whole `traefik` container network.
|
||||
|
||||
To do this:
|
||||
|
||||
- SSH into the machine
|
||||
- run this command to find the network range: `docker network inspect traefik -f "{{ (index .IPAM.Config 0).Subnet }}"` (e.g. `172.19.0.0/16`)
|
||||
- adjust your `vars.yml` configuration to contain a variable like this: `peertube_trusted_proxies_values_custom: ["172.19.0.0/16"]`
|
||||
|
||||
Then, re-install the PeerTube component via the playbook by running: `just install-service peertube`
|
||||
|
||||
You should then see the **Debug** page report your actual IP address.
|
||||
|
|
|
@ -225,7 +225,7 @@
|
|||
name: oxitraffic
|
||||
activation_prefix: oxitraffic_
|
||||
- src: git+https://github.com/mother-of-all-self-hosting/ansible-role-peertube.git
|
||||
version: v6.0.3-0
|
||||
version: v6.0.3-4
|
||||
name: peertube
|
||||
activation_prefix: peertube_
|
||||
- src: git+https://github.com/devture/com.devture.ansible.role.playbook_help.git
|
||||
|
|
Loading…
Reference in a new issue