Add db_ssl as mandatory to v0.17 release notes under the breaking section, or default it to false, when using a pg database #385

Closed
opened 2025-12-29 01:28:02 +01:00 by adam · 0 comments
Owner

Originally created by @MichaelSasser on GitHub (Dec 5, 2022).

Issue description

When I upgraded from v0.16 to headscale/headscale:v0.17, I didn't have db_ssl set in the config. After updating the config according to the breaking section of the release description, I was presented with the following log.

2022-12-05T08:18:16Z FTL go/src/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="cannot parse `host=postgres dbname=headscale user=headscale sslmode= port=5432 password=xxxxx`: failed to configure TLS (sslmode is invalid)"

Adding db_ssl: false resolved the issue.

Originally created by @MichaelSasser on GitHub (Dec 5, 2022). <!-- Headscale is a multinational community across the globe. Our common language is English. Please consider raising the issue in this language. --> **Issue description** When I upgraded from v0.16 to `headscale/headscale:v0.17`, I didn't have `db_ssl` set in the config. After updating the config according to the breaking section of the release description, I was presented with the following log. ```log 2022-12-05T08:18:16Z FTL go/src/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="cannot parse `host=postgres dbname=headscale user=headscale sslmode= port=5432 password=xxxxx`: failed to configure TLS (sslmode is invalid)" ``` Adding `db_ssl: false` resolved the issue.
adam added the bug label 2025-12-29 01:28:02 +01:00
adam closed this issue 2025-12-29 01:28:02 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#385