S3 protocol on Mega

Support
1

Operating system

macOS

Joplin version

3.4.12

Desktop version info

oplin for Desktop

Copyright © 2016-2025 Laurent Cozic
Joplin 3.4.12 (prod, darwin)

Device: darwin, Apple M4
Client ID: 2e24440d293d479b90e9a551e159bce2
Sync Version: 3
Profile Version: 48
Keychain Supported: Yes
Alternative instance ID: -

Revision: e9a9f68

Backup: 1.4.3
Freehand Drawing: 3.1.0

Sync target

S3

What issue do you have?

I am attempting to sync through a S3 bucket hosted at Mega.NZ. The files sync to the bucket, but cannot be synced back down to another client. I get the error message "InvalidRequest Can not identify the requested S3 service." Any ideas what I may be doing wrong?

2

Wouldn't the data on Mega be end to end encrypted? And in which case Joplin probably can't read it

3

They support S3 compatible buckets which can be written to by Joplin.

4

Attaching a full error stack from the log file might help

5

So I got this working. I think the issues were due to my inexperience with S3-compatible buckets.

Here is what worked for me;

S3 bucket: the name you gave your bucket, ideally a guid.

S3 URL: https://s3.g.s4.mega.io

SE Region: Whichever region on Mega you are using for your bucket, ex. ca-central-1

Then just add your Access key and secret key and you should be all set.

1 Like