S3 API Connection Issue in EU-RO-1 (SignatureDoesNotMatch)
I'm having persistent trouble connecting to my Network Volume in the EU-RO-1 data center via the S3-compatible API, and I would be very grateful for some help. I've been trying to troubleshoot this for a while with rclone but keep running into a SignatureDoesNotMatch error.
I believe I have followed all the documented and suggested steps, but I might be missing something. Here is what I have tried so far:
My Setup & Goal:
Tool: rclone on Windows
Datacenter: EU-RO-1
Goal: Simply list the files in my Network Volume (s3://[MY_NETWORK_VOLUMEID]/).
Troubleshooting Steps Taken:
Credentials: I'm using my global RunPod User ID (the user... string) as the access_key_id, as some older documentation suggested. I've also regenerated the Secret Key to be sure.
Clock Sync: I have forced a time sync on my machine using w32tm /resync to rule out clock skew.
rclone Configuration: I have tried many different configurations. My latest attempt is based on advice for non-standard S3 providers and looks like this, but it still results in SignatureDoesNotMatch:
[runpod-s3]
type = s3
provider = Other
access_key_id = user_xxxxxxxxxxxxxxxxxxx # My RunPod User ID
secret_access_key = [MY_SECRET_KEY] # My S3 Secret Key
region = EU-RO-1
endpoint = https://s3api-eu-ro-1.runpod.io
force_path_style = true
s3_auth_version = 2
My Question:
Is there a known issue with the S3 API in the EU-RO-1 endpoint, or is there a specific rclone configuration flag that I might have missed? It seems like I've hit a wall with the standard troubleshooting steps.
Any advice or insight would be greatly appreciated. I'm really looking forward to using this S3 feature!
Thank you!
I believe I have followed all the documented and suggested steps, but I might be missing something. Here is what I have tried so far:
My Setup & Goal:
Tool: rclone on Windows
Datacenter: EU-RO-1
Goal: Simply list the files in my Network Volume (s3://[MY_NETWORK_VOLUMEID]/).
Troubleshooting Steps Taken:
Credentials: I'm using my global RunPod User ID (the user... string) as the access_key_id, as some older documentation suggested. I've also regenerated the Secret Key to be sure.
Clock Sync: I have forced a time sync on my machine using w32tm /resync to rule out clock skew.
rclone Configuration: I have tried many different configurations. My latest attempt is based on advice for non-standard S3 providers and looks like this, but it still results in SignatureDoesNotMatch:
[runpod-s3]
type = s3
provider = Other
access_key_id = user_xxxxxxxxxxxxxxxxxxx # My RunPod User ID
secret_access_key = [MY_SECRET_KEY] # My S3 Secret Key
region = EU-RO-1
endpoint = https://s3api-eu-ro-1.runpod.io
force_path_style = true
s3_auth_version = 2
My Question:
Is there a known issue with the S3 API in the EU-RO-1 endpoint, or is there a specific rclone configuration flag that I might have missed? It seems like I've hit a wall with the standard troubleshooting steps.
Any advice or insight would be greatly appreciated. I'm really looking forward to using this S3 feature!
Thank you!
