Issue connecting to Object Storage using s3cmd
Following this document I tried to setup s3cmd but I get an error:
New settings:
Access Key: ***
Secret Key: ***
Default Region: US
S3 Endpoint: https://ap-south-1.linodeobjects.com
DNS-style bucket+hostname:port template for accessing a bucket: %(bucket)s.ap-south-1.linodeobjects.com
Encryption password:
Path to GPG program: /usr/bin/gpg
Use HTTPS protocol: True
HTTP Proxy server name:
HTTP Proxy server port: 0
Test access with supplied credentials? [Y/n] Y
Please wait, attempting to list all buckets...
ERROR: Test failed: [Errno -3] Temporary failure in name resolution
The key and secret are not the issue, while trying out different configurations it showed the key is correct. Could you advise on what am I missing here?
2 Replies
✓ Best Answer
Hey @storior!
That's definitely a bit out of the ordinary. When I created a bucket and connected to it from my local computer, I was able to do so without an issue. My s3cmd
configs look the same as yours:
New settings:
Access Key: xxxx
Secret Key: xxx
Default Region: us
S3 Endpoint: ap-south-1.linodeobjects.com
DNS-style bucket+hostname:port template for accessing a bucket: %(bucket)s.ap-south-1.linodeobjects.com
Encryption password:
Path to GPG program: None
Use HTTPS protocol: True
HTTP Proxy server name:
HTTP Proxy server port: 0
Test access with supplied credentials? [Y/n] n
Save settings? [y/N] y
Configuration saved to '/Users/tlambert/.s3cfg'
I'm wondering if the Temporary failure in name resolution
was just that, temporary. If not, you may want to make sure you can ping
ap-south-1.linodeobjects.com
to see if a connection is possible from your location.
Additionally, you may want to try some of the troubleshooting steps outlined in this Stack Exchange post titled What does "Temporary failure in name resolution" acctually mean?.
A final suggestion I can offer would be to use another utility to connect to your Object Storage Bucket. Options include the Linode CLI, Cyberduck, or s4cmd.
I hope this helps!