Submitted by balboatech on Sun, 03/15/2015 - 19:22
Hi!
I updated my SSL certificate. A real pain in the butt comodo with 3 certs that need to be combined in a certain order which their docs were out of date on and then it turned out there was a 4th that needed to be included.
I figured I'd nailed it on the first try and used the manage SSL page to copy the configs out to all the other services... Before I got the intermediate/CA/bundle correct.
After updating just the CA Cert we don't get the option to re-copy the config... I was wondering if there was a quick way to manually fire off those scripts again?
Thanks!
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Sun, 03/15/2015 - 22:39 Comment #1
Do you mean re-copy the config to other servers like Postfix and Dovecot?
Submitted by balboatech on Sun, 03/15/2015 - 22:45 Comment #2
Correct
Submitted by JamieCameron on Mon, 03/16/2015 - 00:09 Comment #3
OK, this is a missing feature in Virtualmin - it doesn't look at the chained cert when deciding if copying to other servers is needed or not. This will be fixed in the next release.
Submitted by balboatech on Mon, 03/16/2015 - 11:46 Comment #4
I don't suppose there's a semi-handy way to do the copies manually or trick it into thinking it should make the options available again?
Submitted by andreychek on Mon, 03/16/2015 - 12:31 Comment #5
I'm attaching the patched file for this issue.
If you take the file I've attached, put it in place of your existing file in
/usr/share/webmin/virtual-server/cert_form.cgi
.Once you've replaced that file with the one attached here, restart Webmin with this command:
/etc/init.d/webmin restart
After you do that, does it allow you to copy out those SSL certificates?
Submitted by balboatech on Mon, 03/16/2015 - 13:03 Comment #6
Hitting the manage page now results in: Error - Missing Content-Type Header
Ownership, perms & file names all the same.
The file starts;
/usr/local/bin/perl
which perl/usr/bin/perl
Changed that, the buttons to copy show up!
Very cool. Thanks.
Submitted by Issues on Mon, 03/30/2015 - 13:10 Comment #7
Automatically closed -- issue fixed for 2 weeks with no activity.