Certbot: error: unrecognized arguments: --dns-ovh-credentials ovh.ini

Help
1

Hi! I've used this command to create a certificate using certbot and the OVH DNS plugin:

certbot certonly --dns-ovh --dns-ovh-credentials ovh.ini -d example.com -d www.example.com

but i get:

usage:
  certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
it will attempt to use a webserver both for obtaining and installing the
certificate.
certbot: error: unrecognized arguments: --dns-ovh-credentials ovh.ini

"pip show certbot-dns-ovh" shows the following:

pip show certbot-dns-ovh
Name: certbot-dns-ovh
Version: 2.11.0
Summary: OVH DNS Authenticator plugin for Certbot
Home-page: https://github.com/certbot/certbot
Author: Certbot Project
Author-email: certbot-dev@eff.org
License: Apache License 2.0
Location: C:\Users\<My Username>\AppData\Local\Programs\Python\Python312\Lib\site-packages
Requires: acme, certbot, dns-lexicon, setuptools
Required-by:

so, why wouldnt certbot recognize the argument? I'm running everything from win cmd as administrator and ovh.ini stays in the same folder as execution directory.

2

"certbot plugins" doesnt show the certbot-dns-ovh plugin in the list of plugins. Why isnt certbot finding it? It's installed in the default python directory...

3

Please note that the Certbot team has discontinued Windows support. See Certbot Discontinuing Windows Beta Support in 2024 for more information.

I would advice you to switch to a different ACME client. See e.g. ACME Client Implementations - Let's Encrypt for some options (or in the link above where also some suggestions are made).

1 Like
4

Thanks for the suggestions, but that's not a solution.
I've digged a bit more and presume there might be some issue with Path environment variables of either the user of the system. That could be the reason why certbot doesn't see the plugin. Will continue digging.

5

It doesn't make much sense to expend time/energy into a software that is no longer being maintained, nor recommended by anyone.

You'd be much better served by switching to a currently recommended Windows ACME client.
I've used CertifyTheWeb with complete success.

3 Likes
6

Imagine a guy is coming to you and saying "So here is my old Mercedes w210 and apparently one part of the motor is not working properly". And you'd be like "It doesn't make sense to spend time on this car because it's no longer maintained, just switch to another car".
I know very well what ACME clients are out there and I thought this forum is where I can get help in regard to MY problem and MY conditions.
Therefore, again, thank you for the suggestion, but that's not a solution.

7

Well, to be honest, Certbot on Windows always was a fringe situation. Not many volunteers here have experience with it.

Also, your comparison with the Mercedes isn't quite accurate, as Certbot is free software. Free as in freedom of speech as wel as free as in free beer. The Certbot team is very small and is not a commercial company, thus support will not be the same as what you might expect from a commercial entity. Further more, this is the Let's Encrypt support channel which is, while we often can help people with their Certbot problems, not Certbot-specific. Thus for problems outside of the comfort zone of the volunteerrs, you might not receive any support unfortunately. But maybe you're in luck :slight_smile:

2 Likes
8

Even though there is no such "old car" value in Certbot for Windows...
I will play your [analogy] game:
OK, so you can trade in your "old certbot" for a brand new "CertifyTheWeb" install.
And that upgrade price is zero dollars.
Will you take the deal OR stick with the old broken-down car that no one makes parts for anymore (nor any mechanic will work even on)?

3 Likes
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.