-
“Error! Could not connected to https://s3.dualstack.ap-northeast-1.amazonaws.com/ Failed to fetch” error happens when Test Connection is tried. I also tried https://s3.ap-northeast-1.amazonaws.com/ , but it doesn’t work either. What should I define as the Endpoint URL for S3? I’m referring to https://docs.aws.amazon.com/general/latest/gr/s3.html for the S3 endpoint.
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I found the doc mentioning this setting, but doesn’t replicate. Let me open an issue.
|
Beta Was this translation helpful? Give feedback.
-
I found the correct way for S3. Endpoint URL: empty Tring Test Connection, you would get PM->Connected to successfully! |
Beta Was this translation helpful? Give feedback.
I found the correct way for S3.
Endpoint URL: empty
Access Key: Your access key (e.g. AIMAHHANGEE6XAIW4REV)
Secret Key: Your secret key (e.g. zau3aG9ooxoo1jah7xiocepe+shou1ru9daizeiy)
Region: Your region. The default value, auto desesn’t work for S3 (e.g. ap-northeast-1)
Bucket Name: Your bucket name (e.g. samplebucket)
Use Custom HTTP Handler: On
Tring Test Connection, you would get PM->Connected to successfully!
If you still don’t succeed, View > Toggle Developer Tools > Console is helpful to debug.