Bug #10656

Acme letsencrypt doesn't change private key type

Added by Howard Holm 10 months ago. Updated 9 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


As alluded to in this year and a half old post ( changing the private key configuration item from ECDSDA to RSA appears to succeed, but when re-issuing or renewing the key it silently continues to use the old private key type. At best this is very confusing when the configuration now shows one type of private key, but they system is actually receiving and using a previously configured type.


#1 Updated by Viktor Gurov 10 months ago

  • Status changed from New to Rejected

Duplicate of #10655

Please add any additional comments to that issue.

#2 Updated by Howard Holm 10 months ago

It isn't really a duplicate of that bug. The fallout of that bug sets up the conditions where you might want to change the key type, but the failure to change the type of the key is a completely separate issue. In fact, it looks like the related issue may be fixed with version 4.0 of ntopng. But that fix will have zero effect on this failure to change the key type in ACME.

#3 Updated by Viktor Gurov 10 months ago

  • Status changed from Rejected to Confirmed

Right, got the same issue

#5 Updated by Jim Pingle 10 months ago

  • Status changed from Confirmed to Pull Request Review

#6 Updated by Renato Botelho 9 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100
  • Affected Version deleted (2.4.5-p1)

PR has been merged. Thanks!

Also available in: Atom PDF