Certbot CryptographyDeprecationWarning after updating the OS

Help
1

Hi,

I updated my server OS to the latest. I use Centos 9 stream. I ran a 'dnf update' command. Since then, when I run any 'certbot' command, it is showing warning.

/snap/certbot/4182/lib/python3.12/site-packages/certbot/ocsp.py:238: CryptographyDeprecationWarning: Properties that return a naïve datetime object have been deprecated. Please switch to this_update_utc.
if not response_ocsp.this_update:
/snap/certbot/4182/lib/python3.12/site-packages/certbot/ocsp.py:240: CryptographyDeprecationWarning: Properties that return a naïve datetime object have been deprecated. Please switch to this_update_utc.
if response_ocsp.this_update > now + timedelta(minutes=5):
/snap/certbot/4182/lib/python3.12/site-packages/certbot/ocsp.py:242: CryptographyDeprecationWarning: Properties that return a naïve datetime object have been deprecated. Please switch to next_update_utc.
if response_ocsp.next_update and response_ocsp.next_update < now - timedelta(minutes=5):

How can I fix this? I Googled but not much luck.

This has to be fixed? Or Can I go along with the warning?

Thanks

2

did you update snap images too?

3

This is a known problem but is best posted at the github for Certbot

See this thread but you may want to start a new one to gain greater attention to this. This thread started with a pip install of Certbot but this post and others describe the problem with Certbot snap install for v3.0

4

Thanks for your reply.

I installed Certbot with Snap. Snap will automatically updates to the newest Certbot version. Current version is 3.0.0

Should I be worried? Will Certbot fix this problem? Or I will have to revert to an older version of Certbot? (2.11 or 3834)

When I ran dry-run, it was successful.

Thanks

5

I don't know. I am a volunteer that helps people get and use Let's Encrypt certs.

The developers of Certbot, the EFF, are more easily reached on their github

6

Eventually, probably. I'm a little bit puzzled why it takes so long to be honest. All users are affected by this warning, which is quite irritating.

Note that the current issue for this problem is already very long and I've yet to see a Certbot developer comment.

7

No, me either. If I get time later I'll post something offline in hopes of escalating. But, I suspect you may have done already :slight_smile: