TLS Client error when uploading #217

Closed
opened 2022-09-17 14:28:32 +00:00 by lou_de_sel · 7 comments
Contributor

I'm using Backblaze as an S3 provider and since migrating to Akkoma a few days ago me and people on my instance can't upload anything.

Server side the log outputs theses :

pleroma: request_id=FxWqE0HgPdTJVuYAACjR [warn] ExAws: HTTP ERROR: "TLS client: In state hello_middlebox_assert at ssl_gen_statem.erl:736 generated CLIENT ALERT: Fatal - Unexpected Message\n {unexpected_msg,\n     {internal,\n         {encrypted_extensions,\n             \#{elliptic_curves =>\n                   {supported_groups,\n                       [x25519,secp256r1,secp384r1,secp521r1,x448,ffdhe2048,\n                        ffdhe3072,ffdhe4096,ffdhe6144,ffdhe8192]}}}}}" for URL: "*****REDACTED*****" ATTEMPT: 1

The issue seems to be because of a bug in OTP that was fixed in the last release (only 4 days ago) : https://github.com/erlang/otp/issues/6241

I'm using Backblaze as an S3 provider and since migrating to Akkoma a few days ago me and people on my instance can't upload anything. Server side the log outputs theses : ``` pleroma: request_id=FxWqE0HgPdTJVuYAACjR [warn] ExAws: HTTP ERROR: "TLS client: In state hello_middlebox_assert at ssl_gen_statem.erl:736 generated CLIENT ALERT: Fatal - Unexpected Message\n {unexpected_msg,\n {internal,\n {encrypted_extensions,\n \#{elliptic_curves =>\n {supported_groups,\n [x25519,secp256r1,secp384r1,secp521r1,x448,ffdhe2048,\n ffdhe3072,ffdhe4096,ffdhe6144,ffdhe8192]}}}}}" for URL: "*****REDACTED*****" ATTEMPT: 1 ``` The issue seems to be because of a bug in OTP that was fixed in the last release (only 4 days ago) : https://github.com/erlang/otp/issues/6241

just rebuilding the stable OTP now with the altered version

just rebuilding the stable OTP now with the altered version

should be released

https://ci.akkoma.dev/AkkomaGang/akkoma/build/966

update and try again, let me know if that doesn't fix it

should be released https://ci.akkoma.dev/AkkomaGang/akkoma/build/966 update and try again, let me know if that doesn't fix it
Author
Contributor

I'm using alpine so i use the musl flavor and apparently the job for musl-release failed 😅 (Just tried an update and OTP_VERSION is 24.3.4.4)

I'm using alpine so i use the musl flavor and apparently the job for musl-release failed 😅 (Just tried an update and OTP_VERSION is 24.3.4.4)

ah nice, the one job we needed to succeed failed then, typical

i've restarted it, give it 20 mins (i have no idea why it does that, the CI sometimes randomly interrupts itself, very weird)

ah nice, the one job we needed to succeed failed then, typical i've restarted it, give it 20 mins (i have no idea why it does that, the CI sometimes randomly interrupts itself, very weird)

wahay it succeeded this time, try now

wahay it succeeded this time, try now
Author
Contributor

Yep, it worked and the bug is solved ! Thx a lot !

Yep, it worked and the bug is solved ! Thx a lot !

hooray, party time - thanks for letting me know about the issue

hooray, party time - thanks for letting me know about the issue
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#217
No description provided.