SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided

Operating system

macOS

Joplin version

3.0.1

Desktop version info

Joplin CLI Client

Copyright © 2016-2024 Laurent Cozic
joplin 3.0.1 (prod, darwin)

Client ID: eb530c17ddd14769a74951e0d11b808e
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Sync target

S3

Editor

Markdown Editor

What issue do you have?

I recently upgraded to the latest version of Joplin from 2.9.x to 3.0.1:

Joplin CLI Client

Copyright © 2016-2024 Laurent Cozic
joplin 3.0.1 (prod, darwin)

Client ID: eb530c17ddd14769a74951e0d11b808e
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

I use sync.target.8 which is S3. It had been working properly before the upgrade. Once it's been upgrade it's now having issues.

The issues I am getting are on the AWS target sync:

SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

If related, I am also getting the following error message when opening the application.

keytar.node' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))
    at Module._extensions..node (node:internal/modules/cjs/loader:1717:18)
    at Module.load (node:internal/modules/cjs/loader:1317:32)
    at Module._load (node:internal/modules/cjs/loader:1127:12)
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
    at Module.require (node:internal/modules/cjs/loader:1339:12)
    at require (node:internal/modules/helpers:126:16)
    at Object.<anonymous> (/Users/asaucedo/Programming/lib/node_modules/joplin/node_modules/keytar/lib/keytar.js:1:14)
    at Module._compile (node:internal/modules/cjs/loader:1546:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1691:10) {
  code: 'ERR_DLOPEN_FAILED'
}
(node:19237) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

Let me know if there is an issue with this keytar.node - I assume it may be having issues with the signatures.

Ok I've resolved it. It seems indeed keytar.node was installed with the wrong platform. Installing it with the target solved it.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.