<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Apache on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/apache/</link>
        <description>Recent content in Apache on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Mon, 12 Sep 2016 10:36:40 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/apache/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>[Ubuntu] Secure your Apache 2 Reverse Proxy</title>
            <link>https://www.nico-maas.de/posts/2016-09-12-ubuntu-secure-your-apache-2-reverse-proxy/</link>
            <pubDate>Mon, 12 Sep 2016 10:36:40 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-09-12-ubuntu-secure-your-apache-2-reverse-proxy/</guid>
            <description>&lt;p&gt;We got an Apache 2, working as Reverse Proxy to some Docker instances (we won&amp;rsquo;t talk about the nginx vs Apache stuff here for the same reasons we won&amp;rsquo;t talk about vi vs emacs vs xyz ;)) - and somehow we realized that our apps are a little bit too sensitive to allow them from any ip.&lt;/p&gt;&#xA;&lt;p&gt;First, we want to activate the needed modules. Normally that should not be necessary, but for sake of completeness:&lt;/p&gt;</description>
        </item><item>
            <title>[Ubuntu] Letsencrypt with Apache and Freeradius</title>
            <link>https://www.nico-maas.de/posts/2016-05-16-ubuntu-letsencrypt-with-apache-and-freeradius/</link>
            <pubDate>Mon, 16 May 2016 08:00:53 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-05-16-ubuntu-letsencrypt-with-apache-and-freeradius/</guid>
            <description>&lt;p&gt;This little tutorial describes how to use Letsencrypt with Apache, Freeradius and Auto-Renewal of the Certificates.&lt;/p&gt;&#xA;&lt;h1 id=&#34;install-letsencrypt&#34;&gt;Install Letsencrypt&#xA;&lt;/h1&gt;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;sudo apt-get update  &#xD;&#xA;sudo apt-get install git  &#xD;&#xA;cd /opt  &#xD;&#xA;sudo git clone https://github.com/letsencrypt/letsencrypt /opt/letsencrypt  &#xD;&#xA;cd /opt/letsencrypt&#xD;&#xA;&#xD;&#xA;# Become root  &#xD;&#xA;sudo su&#xD;&#xA;&#xD;&#xA;# &amp;#34;Order&amp;#34; certificates (replace SERVERDOMAIN.COM with the DNS of your Server!)  &#xD;&#xA;./letsencrypt-auto --apache -d SERVERDOMAIN.COM --rsa-key-size 4096  &#xD;&#xA;Enter Contact Mail: mail@SERVERDOMAIN.COM  &#xD;&#xA;Configuration Type: Secure #is best, as it does redirect insecure http to https)&#xD;&#xA;&#xD;&#xA;# Read PATH variable  &#xD;&#xA;echo $PATH&#xD;&#xA;&#xD;&#xA;# Cronjob for certificate renewal  &#xD;&#xA;#you should under all circumstances replace the string following PATH= with your own, as read with the command above.  &#xD;&#xA;#Seperate with ; from the rest of the command like shown in the example  &#xD;&#xA;crontab -e&#xD;&#xA;&#xD;&#xA;# letsencrypt&#xD;&#xA;30 2 * * 1 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;/opt/letsencrypt/letsencrypt-auto renew &amp;amp;gt;&amp;amp;gt; /var/log/le-renew.log&#xD;&#xA;35 2 * * 1 /etc/init.d/freeradius restart&#xD;&#xA;35 2 * * 1 /etc/init.d/apache2 restart&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h1 id=&#34;configure-freeradius&#34;&gt;Configure Freeradius&#xA;&lt;/h1&gt;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;cp -r /etc/freeradius/certs/ /etc/freeradius/certs_bkp  &#xD;&#xA;rm /etc/freeradius/certs/*.pem  &#xD;&#xA;cp /etc/freeradius/eap.conf /etc/freeradius/eap.conf_bkp&#xD;&#xA;&#xD;&#xA;vi /etc/freeradius/eap.conf&#xD;&#xA;&#xD;&#xA;#certdir = ${confdir}/certs&#xD;&#xA;#cadir = ${confdir}/certs&#xD;&#xA;certdir = /etc/letsencrypt/live/SERVERDOMAIN.COM&#xD;&#xA;cadir = /etc/letsencrypt/live/SERVERDOMAIN.COM&#xD;&#xA;#dh_file = ${certdir}/dh&#xD;&#xA;dh_file = ${confdir}/certs/dh&#xD;&#xA;#private_key_password = whatever&#xD;&#xA;private_key_file = ${certdir}/privkey.pem&#xD;&#xA;certificate_file = ${certdir}/cert.pem&#xD;&#xA;CA_file = ${cadir}/fullchain.pem&#xD;&#xA;&#xD;&#xA;# Configure access rights on /etc/letsencrypt  &#xD;&#xA;cd /etc/letsencrypt/  &#xD;&#xA;chgrp -R ssl-cert archive csr keys live options-ssl-apache.conf renewal # set group of cert/key dirs to ssl-cert  &#xD;&#xA;find . -type d -exec chmod g+xs {} \; # directories executable and setguid (set group ssl-cert for new files/dirs)  &#xD;&#xA;find . -type f -exec chmod g+r {} \; # files readable&#xD;&#xA;&#xD;&#xA;# Restart Freeradius  &#xD;&#xA;service freeradius stop  &#xD;&#xA;service freeradius start&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Additional infos: &lt;a class=&#34;link&#34; href=&#34;https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-14-04&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-14-04&lt;/a&gt;&lt;/p&gt;</description>
        </item><item>
            <title>[WinXP/Vista/7] Port 80 Blocked</title>
            <link>https://www.nico-maas.de/posts/2012-11-14-windows-port-80-blocked/</link>
            <pubDate>Wed, 14 Nov 2012 08:09:07 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2012-11-14-windows-port-80-blocked/</guid>
            <description>&lt;p&gt;Developing Websites with XAMPP is always neat and nice: Compact package, everything you need is there - and even having it portable on an USB Stick (in an TrueCrypt file ;)) will get you up and running on every Windows PC - where ever you are - in no time. But the problem with this solution comes with the &amp;ldquo;Host PC&amp;rdquo;: There are a lot of tools nowdays which hijack and use Port 80 (your most beloved Webserver / Apache Standard Port) for their own needs. And so you are quickly on the point of &amp;ldquo;Apache terminated&amp;rdquo; in your XAMPP Windows - because of the blocked port. Finding out which program is blocking / using that port is easy, as XAMPP comes with an &amp;ldquo;Port-Check&amp;rdquo; Tool which can be used from the XAMPP Control Panel. Other than that, here is the TOP 4 of the most annoyning port blocking apps:&lt;/p&gt;</description>
        </item></channel>
</rss>
