Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

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

Posted on February 22, 2023

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

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!

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

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

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

onur.iltan

June 8, 2023

For me it is fixed by giving forcePathStyle as true. I also did not specify bucket name in front of the url

  const s3Client = new S3Client({
      forcePathStyle: true,
      endpoint: process.env.OBJECT_STORAGE_URL,
      region: process.env.OBJECT_STORAGE_REGION,
      credentials: {
        accessKeyId: process.env.OBJECT_STORAGE_KEY,
        secretAccessKey: process.env.OBJECT_STORAGE_SECRET,
      },
    });

Like this

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!

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

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

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

onur.iltan

June 8, 2023

For me it is fixed by giving forcePathStyle as true. I also did not specify bucket name in front of the url

  const s3Client = new S3Client({
      forcePathStyle: true,
      endpoint: process.env.OBJECT_STORAGE_URL,
      region: process.env.OBJECT_STORAGE_REGION,
      credentials: {
        accessKeyId: process.env.OBJECT_STORAGE_KEY,
        secretAccessKey: process.env.OBJECT_STORAGE_SECRET,
      },
    });

Like this

Report this

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

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today