similar to: audit freeing multiple contexts (when running certbot)

Displaying 20 results from an estimated 3000 matches similar to: "audit freeing multiple contexts (when running certbot)"

2020 Oct 05
0
certbot stopped working on CentOS 7: pyOpenSSL module missing required functionality
> On Oct 5, 2020, at 7:04 AM, Alexander Farber <alexander.farber at gmail.com> wrote: > > Hello fellow CentOS users, > > I had this cronjob working for many moons on CentOS 7.8.2003: > > #minute hour mday month wday command > 6 6 * * 1 certbot renew --post-hook > "cat
2020 Oct 05
2
certbot stopped working on CentOS 7: pyOpenSSL module missing required functionality
Hello fellow CentOS users, I had this cronjob working for many moons on CentOS 7.8.2003: #minute hour mday month wday command 6 6 * * 1 certbot renew --post-hook "cat /etc/letsencrypt/live/raspasy.de/fullchain.pem /etc/letsencrypt/live/ raspasy.de/privkey.pem > /etc/letsencrypt/live/raspasy.de/haproxy.pem; systemctl resstart
2020 Nov 12
1
Fwd: Trying to install certbot on CentOS
On 11/12/2020 10:44 AM, Raymond Herrera wrote: > Following the advice obtained here, I am trying to get a LetsEncrypt > certificate. > > These are the instructions: > > Step 1: > https://snapcraft.io/docs/installing-snapd > > Step 2: > https://certbot.eff.org/lets-encrypt/centosrhel7-apache > > My problem is this error message: > > # snap install
2020 Nov 12
2
Trying to install certbot on CentOS
Following the advice obtained here, I am trying to get a LetsEncrypt certificate. These are the instructions: Step 1: https://snapcraft.io/docs/installing-snapd Step 2: https://certbot.eff.org/lets-encrypt/centosrhel7-apache My problem is this error message: # snap install --classic certbot error: system does not fully support snapd: cannot mount squashfs image using "squashfs":
2020 Oct 05
0
certbot stopped working on CentOS 7: pyOpenSSL module missing required functionality
Not directly an answer to your question, but we had so many problems with the certbot in different constellations, that we moved to https://github.com/acmesh-official/acme.sh which works just fine basically everywhere cheers Soeren ?On 05.10.20, 15:18, "CentOS on behalf of Alexander Farber" <centos-bounces at centos.org on behalf of alexander.farber at gmail.com> wrote:
2018 Sep 15
1
icecast ssl and letsencrypt renewal
Install letsencrypt and request a certificate specifying the webroot of your Icecast server and the host.domain: certbot-auto certonly --webroot --webroot-path /usr/share/icecast2/web/ -d icecast.domain.name Now you should have a certificate for your server, it's only in the wrong format for Icecast, copy the key and the certificate to 1 file with the following cmd: cat
2019 Mar 14
0
Re: Am I right to assume certificate renewal with the same filename requires a dovecot reload/restart
On Thu, Mar 14, 2019, at 11:33 AM, Yassine Chaouche via dovecot wrote: > On 3/14/19 9:32 AM, Yassine Chaouche via dovecot wrote: > > The general answere here is try and see, as you could totally test it > > on your own. The certificate is read at startup and put in memory for > > the rest of the execution time. Dovecot won't monitor the file for > > changes on
2020 Oct 09
0
Feature request.
Automatic renewal The Ubuntu package for certbot comes pre-configured with systemd timer that will automatically renew existing certificates. What it does not handle however is reloading postfix/dovecot so that they will begin using the new certificates. For that, we need to implement a hook. Certbot has both pre and post hooks that you can use to execute a script prior to and after the renewal
2020 Oct 05
2
certbot stopped working on CentOS 7: pyOpenSSL module missing required functionality
Yes, I had a typo in the mail, but not in the cronjob Still wondering how to get certbot-1.7.0-1.el7.noarch working on CentOS 7 again.
2010 Feb 03
1
[PATCH] Re: name_count maxed, losing inode data: dev=00:05, inode=5221
Ralf Hildebrandt reported[0] the following messages on ext3-users: name_count maxed, losing inode data: dev=00:05, inode=5221 because the filesystem in question is indeed ext3. However, this warning is not generated by ext3 code but by the audit framework. While the origins of these messages are discussed elsewhere[1] the following patch modifies the printks in question so that users know
2017 Sep 12
1
Dovecot and Letsencrypt certs
On Tue, 12 Sep 2017, dovecot-request at dovecot.org wrote: > What's wrong with using a certbot "post-hook" script such as: > > #!/bin/bash > echo "Letsencrypt renewal hook running..." > echo "RENEWED_DOMAINS=$RENEWED_DOMAINS" > echo "RENEWED_LINEAGE=$RENEWED_LINEAGE" > > if grep --quiet "your.email.domain" <<<
2018 Jul 10
3
Certbot error CentOS 7.5
Hi All - I am running CentOS 7.5 and trying to use certbot. I am getting an error 403 forbidden on the /.well-known/acme-challenge/-CG_gSckofY5ln7TdMvoanDI1_FBRh8otQkyB0hxmoo Some searching indicated permission problems... I also noticed that the /var/www/html directory does not even have the .well-known directory in it. The /var/www/html directory was root:root I changed it to root:apache
2018 Sep 06
0
icecast ssl and letsencrypt renewal
Hello, How did you get icecast and letsencrypt certificates working? Thanks. Dave. On 9/6/18, _zer0_ gravity <zer0___ at hotmail.com> wrote: > That’s what I have been looking for, thanks ! > > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Tycho Eggen > Sent: donderdag 6 september 2018 22:21 > To: Icecast streaming server user discussions > Subject: Re:
2017 Mar 03
0
letsencrypt
On 2017-03-03 19:07, David Mehler wrote: > Hello, > > I know some users here are using letsencrypt for their CA. If this is > to off topic write me privately. > > I'm wanting letsencrypt to take over as my CA, replacing existing self > signed certificates. I've got web working, a certificate for https > sites and one for webmail as they have different names. What
2017 Mar 03
3
letsencrypt
Hello, Thanks. Is there another way of doing this? I've got a web server running on 80 and 443. Are there any other options? Thanks. Dave. On 3/3/17, Michael Neurohr <mine at michi.su> wrote: > On 2017-03-03 19:07, David Mehler wrote: >> Hello, >> >> I know some users here are using letsencrypt for their CA. If this is >> to off topic write me privately.
2018 Sep 06
2
icecast ssl and letsencrypt renewal
That’s what I have been looking for, thanks ! From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Tycho Eggen Sent: donderdag 6 september 2018 22:21 To: Icecast streaming server user discussions Subject: Re: [Icecast] icecast ssl and letsencrypt renewal You can add a posthook to your certbot cronjob: certbot renew —post-hook “/etc/init.d/icecast restart” Or however you restart
2017 Sep 12
2
Dovecot and Letsencrypt certs
And remove that "postfix reload" command - Postfix doesn't require explicit reloading. It'll pickup the changed cert automagically. Daniel On 9/12/2017 9:26 AM, Daniel Miller wrote: > What's wrong with using a certbot "post-hook" script such as: > > #!/bin/bash > echo "Letsencrypt renewal hook running..." > echo
2018 Sep 06
0
icecast ssl and letsencrypt renewal
You can add a posthook to your certbot cronjob: certbot renew —post-hook “/etc/init.d/icecast restart” Or however you restart icecast On Thu, Sep 6, 2018 at 13:05 _zer0_ gravity <zer0___ at hotmail.com> wrote: > Hi all, > > > > I have setup icecast to work with letsencrypt ssl certificate, this works > fine. > > But now I am struggling a bit on how to renew the
2020 Nov 12
0
How do Cerbot files map to Dovecot?
On Thu, 12 Nov 2020, Raymond Herrera wrote: > I am postponing the Apache plugin issue (CentOS is not Certbot friendly) and For the record, certbot works just fine on CentOS. It just requires that you understand how things work. :-) The plugin which you seek is called python2-certbot-apache.noarch. You can see all of the available plugins on CentOS 7 by running the following: yum list
2019 Jan 10
0
repo.dovecot.org expired certificate
On 10.1.2019 9.42, Filipe Carvalho wrote: > > Hello, > > Not sure if this is the right place to post this, but the ssl > certificate of the repo.dovecot.org server expired on the 9th of January. > > It's giving an error via the browser and via the apt command in Debian: > > W: Failed to fetch >