`mongodump` doesn't like my self-signed certificate

Working with Data
, , , ,
1

I’m using a self-signed certificate in development, and my PHP, Python, and Node.js code works fine using appropriate options in the MongoDB URI.

However, mongodump is not happy. Various combinations of the same sort of options to mongodump yield errors such as:

Type: Unknown, Last error: connection() error occurred during connection handshake: x509: certificate relies on legacy Common Name field, use SANs instead

Is there any “quick fix” to make mongodump work, or do I need to regen my certificate?

2

Hi @Jack_Woehr,
I think you need to regen your certificate.

Best regards

1 Like
3

Yes, I thought that might be the answer … :grin:

1 Like
4

Hi @Jack_Woehr If you’re in a pinch you could try older versions of MongoDB Database Tools.

1 Like
5

Thanks, @chris , but that sounds like learning to limp on the other foot :grin:
If the rule is going forward that the certificate has to use SAN instead of Common Name, I might as well adapt.