<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Nginx on Tux-Sudo</title><link>https://blog.tux-sudo.com/tags/nginx/</link><description>Recent content in Nginx on Tux-Sudo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 19 Feb 2018 11:01:54 +0530</lastBuildDate><atom:link href="https://blog.tux-sudo.com/tags/nginx/index.xml" rel="self" type="application/rss+xml"/><item><title>Caddy! Team 443 FTW</title><link>https://blog.tux-sudo.com/posts/caddy-autohttps/</link><pubDate>Mon, 19 Feb 2018 11:01:54 +0530</pubDate><guid>https://blog.tux-sudo.com/posts/caddy-autohttps/</guid><description>&lt;p&gt;This one is a gamechanger. It really is.&lt;/p&gt;
&lt;p&gt;On a recent Golang obsessed Github browsing spree, I read the following project description: &amp;ldquo;Fast, cross-platform HTTP/2 web server with automatic HTTPS&amp;rdquo;. I&amp;rsquo;ve read that before, and more often than not ended up disappointing myself and resorting to hacks like [this] (&lt;a href="https://blog.tux-sudo.com/posts/letsencrypt-nginx-docker/"&gt;https://blog.tux-sudo.com/posts/letsencrypt-nginx-docker/&lt;/a&gt;) to create an automatic TLS system for my websites. There are other ways, but almost all of them were semi-automatic in the long run (yay cron!). I decided to try out [Caddy] (&lt;a href="https://caddyserver.com/)"&gt;https://caddyserver.com/)&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>LetsEncrypt Certificates for Dockerized Nginx</title><link>https://blog.tux-sudo.com/posts/letsencrypt-nginx-docker/</link><pubDate>Tue, 26 Sep 2017 16:25:49 +0530</pubDate><guid>https://blog.tux-sudo.com/posts/letsencrypt-nginx-docker/</guid><description>&lt;p&gt;I like nginx. I like docker. I like SSL. I also like not paying for SSL certificates.&lt;br&gt;
If you, like me are operating a small time website, you probably don&amp;rsquo;t want to dish out a few hundred dollars for an SSL certificate.Thankfully, &lt;a href="https://letsencrypt.org"&gt;LetsEncrypt&lt;/a&gt; provides &lt;strong&gt;free&lt;/strong&gt; ssl certificates and is now trusted by most major browsers.&lt;br&gt;
However, integrating &lt;a href="https://certbot.eff.org/"&gt;certbot&lt;/a&gt; to automatically configure my nginx inside a docker container has been a pain. In the past, I generated the standalone cert with &amp;ndash;cert-only and then linked my docker container to use it but this was a far from usable solution given the horrid automation code I had to write. &lt;br&gt;
Recently, I tried to come up with a more automation friendly solution and ended up with the following:&lt;br&gt;&lt;/p&gt;</description></item></channel></rss>