Question

Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames:

when I tried to upload using node.js @aws-sdk/client-s3 setup

error message this 👇

Host: <BUCKET_NAME>.<BUCKET_NAME>.nyc3.digitaloceanspaces.com. is not in the cert's altnames: DNS:*.nyc3.digitaloceanspaces.com, DNS:nyc3.digitaloceanspaces.com

Submit an answer


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
February 23, 2023
Accepted Answer

Hi there,

The configuration should look as follows:

import { S3 } from "@aws-sdk/client-s3";

const s3Client = new S3({
    forcePathStyle: false, // Configures to use subdomain/virtual calling format.
    endpoint: "https://nyc3.digitaloceanspaces.com",
    region: "us-east-1",
    credentials: {
      accessKeyId: process.env.SPACES_KEY,
      secretAccessKey: process.env.SPACES_SECRET
    }
});

export { s3Client };

You don’t have to specify the bucket name in front of the nyc3.digitaloceanspaces.com hostname:

https://docs.digitalocean.com/products/spaces/reference/s3-sdk-examples/

Let me know how it goes!

Best,

Bobby

alexdo
Site Moderator
Site Moderator badge
February 25, 2023

Hello @swimmingaquamarinedolphin

There is no need to specify the bucket name in front of the endpoint itself. The link which Bobby provided will give you good examples on how to use s3 client.

You can also explore other tools like s3cmd

https://docs.digitalocean.com/products/spaces/reference/s3cmd/

Regards

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up