Skip to content

Bump Ktor to 3.4.0 to fix SSL on linuxArm64#221

Open
sbounmy wants to merge 1 commit intoACINQ:masterfrom
sbounmy:fix/ktor-3.4.0-arm64-ssl
Open

Bump Ktor to 3.4.0 to fix SSL on linuxArm64#221
sbounmy wants to merge 1 commit intoACINQ:masterfrom
sbounmy:fix/ktor-3.4.0-arm64-ssl

Conversation

@sbounmy
Copy link

@sbounmy sbounmy commented Feb 23, 2026

Problem

Ktor 3.3.0 ships a bundled libcurl for linuxArm64 that has no default CA certificate path compiled in. This means every outgoing HTTPS request (e.g. webhook delivery) fails with:

peer certificate cannot be authenticated with given CA certificates

TLS verification fails because libcurl cannot locate system CA certificates on ARM64 Linux hosts.

This is tracked upstream as KTOR-8339.

Fix

Bump Ktor from 3.3.0 to 3.4.0, which includes the fix for KTOR-8339.

Changes

  • gradle/libs.versions.toml: ktor = "3.3.0"ktor = "3.4.0"

Ktor 3.3.0 ships a bundled libcurl for linuxArm64 that has no
default CA certificate path compiled in, so every outgoing HTTPS
request (e.g. webhook delivery) fails with "peer certificate cannot
be authenticated with given CA certificates" / TLS verification
failed.

This is tracked upstream as KTOR-8339 and fixed in Ktor 3.4.0.
@pm47
Copy link
Member

pm47 commented Feb 23, 2026

Hello, this is a known limitation (I authored the Ktor issue that you linked ), for which we had a workaround in ACINQ/lightning-kmp#777. Did the workaround fail in your case?

@sbounmy
Copy link
Author

sbounmy commented Feb 23, 2026

yes it didn't work I had TLS verification failed for request whenever a webhook was tryign to trigger

using phoenixd version 0.7.2-1b6c08d

@pm47
Copy link
Member

pm47 commented Feb 23, 2026

What OS are you using?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants