# Problems With S3 Object Storage

**URL:** <https://discourse.joplinapp.org/t/problems-with-s3-object-storage/44385>\
**Category:** Beta Testing\
**Created:** [15 March 2025 05:22 UTC](https://discourse.joplinapp.org/t/problems-with-s3-object-storage/44385 "2025-03-15T05:22:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zagone](https://avatars.discourse-cdn.com/v4/letter/z/f14d63/32.png) [@Zagone](https://discourse.joplinapp.org/u/Zagone)\
**Post date:** [15 March 2025 05:22 UTC](https://discourse.joplinapp.org/t/problems-with-s3-object-storage/44385/1 "2025-03-15T05:22:32Z")

</div>

I'm trying to initiate an S3 object storage sync with os.alp2.flow.swiss

Flow Swiss does not use regions or endpoints.

With Cyberduck, I am able to type in any old AWS region and it will work. I have done that here (Region: us-east-1).

The "Check Synchronisation Configuration" indicates success when I do this in Joplin Linux.

The following error message is with "force path style" checked, and encryption enabled -- but I get the same or very similar error message with force path unchecked and no encryption.

Any ideas? THANK YOU!

```auto
Error

The sync target could not be upgraded due to an error. For support, please copy the complete content of this page and paste it in the forum: https://discourse.joplinapp.org/

The full error was:

Could not upgrade from version 1 to version 2: write after end

Error [ERR_STREAM_WRITE_AFTER_END]: Could not upgrade from version 1 to version 2: write after end
    at ClientRequest.end (node:_http_outgoing:1043:15)
    at writeBody (/tmp/.mount_Joplinx59G0v/resources/app.asar/node_modules/@joplin/lib/node_modules/@aws-sdk/node-http-handler/dist-cjs/write-request-body.js:22:21)
    at ClientRequest.<anonymous> (/tmp/.mount_Joplinx59G0v/resources/app.asar/node_modules/@joplin/lib/node_modules/@aws-sdk/node-http-handler/dist-cjs/write-request-body.js:9:13)
    at ClientRequest.emit (node:events:519:28)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:645:11)
    at HTTPParser.parserOnHeadersComplete (node:_http_common:118:17)
    at TLSSocket.socketOnData (node:_http_client:544:22)
    at TLSSocket.emit (node:events:519:28)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
```
