Also use 127.0.0.1 for database and redis

Node 18 can resolve localhost to IPv6 address, where postgresql and/or
redis may listen on IPv4 only
This commit is contained in:
Chocobozzz 2023-11-07 10:40:08 +01:00
parent 2d4274769e
commit 1ba8bbded0
No known key found for this signature in database
GPG Key ID: 583A612D890159BE
4 changed files with 7 additions and 7 deletions

View File

@ -11,7 +11,7 @@ We have many important notes in this release. We know it's a pain for sysadmin,
* Remove NodeJS 16 support (see https://nodejs.org/fr/blog/announcements/nodejs16-eol): * Remove NodeJS 16 support (see https://nodejs.org/fr/blog/announcements/nodejs16-eol):
* Please upgrade to NodeJS 18 before upgrading PeerTube * Please upgrade to NodeJS 18 before upgrading PeerTube
* If you use NodeSource repository, you may have to migrate to their new repository: https://github.com/nodesource/distributions/wiki/How-to-migrate-to-the-new-repository * If you use NodeSource repository, you may have to migrate to their new repository: https://github.com/nodesource/distributions/wiki/How-to-migrate-to-the-new-repository
* Check in `production.yaml` that you use `127.0.0.1` instead of `localhost` for `listen.hostname` (https://github.com/Chocobozzz/PeerTube/blob/develop/config/production.yaml.example#L2) to ensure PeerTube is listening on IPv4 * Check in `production.yaml` that you use `127.0.0.1` instead of `localhost` for `listen.hostname`, `database.hostname` and `redis.hostname` as Node 18 favours IPv6 for `localhost` resolution
* Remove WebTorrent support in player: * Remove WebTorrent support in player:
* "WebTorrent videos" are renamed to "Web Video". The video format is the same, we just stop to use P2P for these videos * "WebTorrent videos" are renamed to "Web Video". The video format is the same, we just stop to use P2P for these videos

View File

@ -70,7 +70,7 @@ trust_proxy:
# Your database name will be database.name OR 'peertube'+database.suffix # Your database name will be database.name OR 'peertube'+database.suffix
database: database:
hostname: 'localhost' hostname: '127.0.0.1'
port: 5432 port: 5432
ssl: false ssl: false
suffix: '_dev' suffix: '_dev'
@ -83,7 +83,7 @@ database:
# You can also specify a 'socket' path to a unix socket but first need to # You can also specify a 'socket' path to a unix socket but first need to
# set 'hostname' and 'port' to null # set 'hostname' and 'port' to null
redis: redis:
hostname: 'localhost' hostname: '127.0.0.1'
port: 6379 port: 6379
auth: null # Used by both standalone and sentinel auth: null # Used by both standalone and sentinel
db: 0 db: 0

View File

@ -17,11 +17,11 @@ rates_limit:
max: 200 max: 200
database: database:
hostname: 'localhost' hostname: '127.0.0.1'
port: 5432 port: 5432
redis: redis:
hostname: 'localhost' hostname: '127.0.0.1'
smtp: smtp:
hostname: null hostname: null

View File

@ -68,7 +68,7 @@ trust_proxy:
# Your database name will be database.name OR 'peertube'+database.suffix # Your database name will be database.name OR 'peertube'+database.suffix
database: database:
hostname: 'localhost' hostname: '127.0.0.1'
port: 5432 port: 5432
ssl: false ssl: false
suffix: '_prod' suffix: '_prod'
@ -81,7 +81,7 @@ database:
# You can also specify a 'socket' path to a unix socket but first need to # You can also specify a 'socket' path to a unix socket but first need to
# set 'hostname' and 'port' to null # set 'hostname' and 'port' to null
redis: redis:
hostname: 'localhost' hostname: '127.0.0.1'
port: 6379 port: 6379
auth: null # Used by both standalone and sentinel auth: null # Used by both standalone and sentinel
db: 0 db: 0