Unable to access S3 using 9.3 or newer

[DM1145]

Opening S3 buckets on Version 9.2.4 (43667) works.

Opening the same connections on Version 9.3 or later results in the error "The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. Please contact your web hosting service provider for assistance."

Apple M4 Max Mac / OS 26.1

No entries in Cyberduck log (deleted log file and tested)

[nodakai]

Yeah my 9.3.1 is broken. FYI #17690

[DM1145]

Yeah my 9.3.1 is broken. FYI #17690

Unfortunately, I'm not using STS or SSO token credentials. Just a static access key and secret.

[atloiaco]

Not working for me either, had to roll back to an earlier version. Also using a static key and secret

[dkocher]

Most likely the S3 (Credentials from AWS Command Line Interface) profile installed is missing a recent configuration change now required. Open Preferences → Profiles to sync the latest version. You can verify on disk with

md5sum ~/Library/Group\ Containers/G69SCX94XU.duck/Library/Application\ Support/duck/Profiles/S3\ \(Credentials\ from\ AWS\ Command\ Line\ Interface\).cyberduckprofile 

The output should match ee93d6f70890eb8b1adfb4aa0d8a2177.

[atloiaco]

I only had this issue after upgrading to 9.3 from using the same bookmark. Ended up running both in parallel from different directories and the credentials work on < 9.3 but not 9.3

[captify-omomot]

hm, first - not good to break something that was working before(without explicit warning at least)
my aws keys works in aws cli, but I'm getting this error in Duck.
Preferences Settings → Profiles spins for a minute and brings damn long list of something I dunno what to select. (okay, selected some AWS S3... ), but the issue still there, it fails to Login

[dkocher]

Can you please attach a debug log to allow us to determine the cause of the continuous issues.

[captify-omomot]

nothing in log stream --predicate '(process == "Cyberduck") && (category == "transcript")' --level info when trying to open bookmark.
Console shows this(not sure it is related somehow...)

2025-12-16 11:34:05,748 [Thread-64] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol manta in profile. Try fallback with no predicate in lookup
2025-12-16 11:34:23,486 [Thread-64] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol irods in profile. Try fallback with no predicate in lookup
2025-12-16 11:34:35,841 [Thread-64] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol irods in profile. Try fallback with no predicate in lookup
2025-12-16 11:35:00,199 [Thread-64] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol irods in profile. Try fallback with no predicate in lookup
2025-12-16 11:35:04,852 [Thread-64] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol hubic in profile. Try fallback with no predicate in lookup
2025-12-16 11:35:12,041 [Thread-64] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol spectra in profile. Try fallback with no predicate in lookup
2025-12-16 11:35:29,191 [Thread-64] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol sharepoint-site in profile. Try fallback with no predicate in lookup
2025-12-16 12:06:13,118 [Thread-103] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol spectra in profile. Try fallback with no predicate in lookup
2025-12-16 12:06:16,966 [Thread-103] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol manta in profile. Try fallback with no predicate in lookup
2025-12-16 12:06:30,348 [Thread-103] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol irods in profile. Try fallback with no predicate in lookup
2025-12-16 12:06:41,535 [Thread-103] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol irods in profile. Try fallback with no predicate in lookup
2025-12-16 12:07:04,350 [Thread-103] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol irods in profile. Try fallback with no predicate in lookup
2025-12-16 12:07:09,367 [Thread-103] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol hubic in profile. Try fallback with no predicate in lookup
2025-12-16 12:07:14,399 [Thread-103] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol spectra in profile. Try fallback with no predicate in lookup
2025-12-16 12:07:29,599 [Thread-103] ERROR ch.cyberduck.core.serializer.ProfileDictionary - Unknown protocol sharepoint-site in profile. Try fallback with no predicate in lookup

confusing part, that I have 5 profiles, and one of them works, but 4 are not. all works in aws cli.

[DM1145]

As noted in my original post, I deleted the cyberduck log in the console and retried to connect.
No entries were written to the log.