Migrate from AWS S3 to Railway Storage
service
PROOP

a month ago

I am trying to migrate my buckets from AWS S3 to Railway Storage. I enter key/Secret and everything works fine until to execute migration by using following command.

.\rclone.exe sync aws:bucket_to_migrate railway:bucket_to_migrate --dry-run --progress

while executing command I get the following error:

Attachments

Solved$20 Bounty

1 Replies

Status changed to Open Railway about 1 month ago


Status changed to Awaiting User Response Railway about 1 month ago


service
PROOP

a month ago

Hi,

below you can find the error log of sync..

"""

velopment railway:bucket_To_migrate --dry-run --progress

2026/05/11 16:07:16 ERROR : S3 bucket_To_migrate: error reading source root directory: operation error S3: ListObjectsV2, https response error StatusCode: 403, RequestID: CWRS1WYCR6V4G3W5, HostID: hahahahah/, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

2026/05/11 16:07:16 ERROR : S3 bucket_To_migrate: not deleting files as there were IO errors

2026/05/11 16:07:16 ERROR : S3 bucket_To_migrate: not deleting directories as there were IO errors

2026/05/11 16:07:16 ERROR : Attempt 1/3 failed with 1 errors and: operation error S3: ListObjectsV2, https response error StatusCode: 403, RequestID: CWRS1WYCR6V4G3W5, HostID: akkakakakakkaka/, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

2026/05/11 16:07:16 ERROR : S3 bucket_To_migrate: error reading source root directory: operation error S3: ListObjectsV2, https response error StatusCode: 403, RequestID: CWRHW28N4ZCBFBZN, HostID: +j20T2OuvApOWdEQEHhHkVnO/rrbbJISuhiv8S4kaH1KeehTS90o2PWuA7qZWRpnfdH5/WlV0Tx4xHayWr+3cf2i3iWahMLt, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

2026/05/11 16:07:16 ERROR : S3 bucket_To_migrate: not deleting files as there were IO errors

2026/05/11 16:07:16 ERROR : S3 bucket_To_migrate: not deleting directories as there were IO errors

2026/05/11 16:07:16 ERROR : Attempt 2/3 failed with 1 errors and: operation error S3: ListObjectsV2, https response error StatusCode: 403, RequestID: CWRHW28N4ZCBFBZN, HostID: shshshshs, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

2026/05/11 16:07:16 ERROR : S3 bucket_To_migrate: error reading source root directory: operation error S3: ListObjectsV2, https response error StatusCode: 403, RequestID: CWRNSPZJN27EESJ6, HostID: kakakakkaka, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

2026/05/11 16:07:16 ERROR : S3 bucket_To_migrate: not deleting files as there were IO errors

2026/05/11 16:07:16 ERROR : S3 bucket_To_migrate: not deleting directories as there were IO errors

2026/05/11 16:07:16 ERROR : Attempt 3/3 failed with 1 errors and: operation error S3: ListObjectsV2, https response error StatusCode: 403, RequestID: CWRNSPZJN27EESJ6, HostID: kakakakakkakak, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

Transferred: 0 B / 0 B, -, 0 B/s, ETA -

Errors: 1 (retrying may help)

Elapsed time: 0.1s

2026/05/11 16:07:16 NOTICE:

Transferred: 0 B / 0 B, -, 0 B/s, ETA -

Errors: 1 (retrying may help)

Elapsed time: 0.1s

2026/05/11 16:07:16 NOTICE: Failed to sync: operation error S3: ListObjectsV2, https response error StatusCode: 403, RequestID: CWRNSPZJN27EESJ6, HostID: hahhahahhaha, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

"""


Status changed to Awaiting Railway Response Railway about 1 month ago


Status changed to Solved service about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...