<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Https - Tag - vo.rs</title><link>https://vo.rs/tags/https/</link><description>Https - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 31 Mar 2026 13:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/https/" rel="self" type="application/rss+xml"/><item><title>Reverse Proxy Done Right: Automatic HTTPS with Caddy in Ten Minutes</title><link>https://vo.rs/story/reverse-proxy-done-right-automatic-https-with-caddy/</link><description>&lt;p&gt;If you have ever wrestled with certificate files, cron jobs that renew them, and a configuration syntax that feels designed to punish typos, you will appreciate what follows. There is a web server that obtains valid HTTPS certificates for you, renews them before they expire, and routes traffic to your applications using a configuration file short enough to read in a single breath. It is called Caddy, and by the end of this guide you will have two services sitting safely behind it with proper TLS, no manual certificate handling, and roughly ten minutes of effort. This is what a reverse proxy is supposed to feel like.&lt;/p&gt;</description><pubDate>Tue, 31 Mar 2026 13:00:00 +0000</pubDate></item></channel></rss>