openssl rand -base64 32 for POSTGRES_PASSWORD. That password goes into postgres://flamenet:<password>@db:5432/flamenetunencoded, and base64 emits / or +72.9% of the time — measured over 20k samples, not estimated.
A / ends the URL authority, so the relay dies at start-up with a bare Code=-1000 and the connection string echoed back — which reads like the
database is unreachable rather than like the password needs escaping.
So roughly three self-hosters in four followed these instructions and got a
relay that would not start, for a reason the error never mentions.
The relay-s own .env.example has carried the correct instruction, and an
explanation of exactly this, for some time. This file disagreed with the file it
tells people to copy — and this is the one they read first.
`openssl rand -base64 32` for `POSTGRES_PASSWORD`. That password goes into
`postgres://flamenet:<password>@db:5432/flamenet` **unencoded**, and base64 emits
`/` or `+` **72.9% of the time** — measured over 20k samples, not estimated.
A `/` ends the URL authority, so the relay dies at start-up with a bare
`Code=-1000` and the connection string echoed back — which reads like the
database is unreachable rather than like the password needs escaping.
So roughly **three self-hosters in four** followed these instructions and got a
relay that would not start, for a reason the error never mentions.
The relay-s own `.env.example` has carried the correct instruction, and an
explanation of exactly this, for some time. This file disagreed with the file it
tells people to copy — and this is the one they read first.
Found by a job that runs these steps rather than reading them:
paulhitt/flamenet-relay!8.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
openssl rand -base64 32forPOSTGRES_PASSWORD. That password goes intopostgres://flamenet:<password>@db:5432/flamenetunencoded, and base64 emits/or+72.9% of the time — measured over 20k samples, not estimated.A
/ends the URL authority, so the relay dies at start-up with a bareCode=-1000and the connection string echoed back — which reads like thedatabase is unreachable rather than like the password needs escaping.
So roughly three self-hosters in four followed these instructions and got a
relay that would not start, for a reason the error never mentions.
The relay-s own
.env.examplehas carried the correct instruction, and anexplanation of exactly this, for some time. This file disagreed with the file it
tells people to copy — and this is the one they read first.
Found by a job that runs these steps rather than reading them:
paulhitt/flamenet-relay!8.
mentioned in commit
40fd2f51d4mentioned in issue flamenet-relay#10
mentioned in commit flamenet-relay@329e539461eaa21f6857840413488e1cb3cdc007
mentioned in merge request flamenet-relay!9
mentioned in merge request flamenet-relay!8
changed the description