<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Let's Encrypt on Michael’s Domain</title><link>https://jeltsch.org/en/tags/lets-encrypt/</link><description>Recent content in Let's Encrypt on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/lets-encrypt/index.xml" rel="self" type="application/rss+xml"/><item><title>Let's encrypt duplicated my log files</title><link>https://jeltsch.org/en/let_s_encrypt_duplicated_my_log_files/</link><pubDate>Wed, 19 Oct 2016 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/let_s_encrypt_duplicated_my_log_files/</guid><description>&lt;p&gt;I have not been keeping log files for my web server until the beginning of 2016, when I needed to trace access to certain files (I started to use 
 &lt;a href="http://www.awstats.org/" target="_blank" rel="noopener noreferrer nofollow"&gt;awstats&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
, mostly because I was familiar with it since I had used it years ago when my site was still running on a Red Hat server). In March 2016 I luckily started to use 
 &lt;a href="https://letsencrypt.org/" target="_blank" rel="noopener noreferrer nofollow"&gt;Let’s Encrypt&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
. I had used another &amp;ldquo;free&amp;rdquo; service before, which got recently into big trouble as they apparently had not control over their own security. When I looked at my Apache server&amp;rsquo;s log files (on Ubuntu 14.04), I noticed that apache did double logging (to both the individual vhost&amp;rsquo;s log file and a common log file). I realized that Let&amp;rsquo;s Encrypt specifies into every vhost&amp;rsquo;s configuration file an Import directive which sources /etc/letsencrypt/options-ssl-apache.conf. And this file in turn specifies common access.log and error.log files for all vhosts in the /var/log/apache2/ directory. I uncommented the five lines associated with this logging and the duplicate logging stopped (originally, I had thought, that this letsencrypt directive was only used for the initial Let&amp;rsquo;s Encrypt setup for the cert generation).&lt;/p&gt;</description></item></channel></rss>