<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ssl on The Home Lab</title><link>https://adamazl.github.io/homelab/tags/ssl/</link><description>Recent content in Ssl on The Home Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 15 Mar 2026 00:37:20 +1300</lastBuildDate><atom:link href="https://adamazl.github.io/homelab/tags/ssl/index.xml" rel="self" type="application/rss+xml"/><item><title>Reverse Proxy and SSL with Nginx Proxy Manager</title><link>https://adamazl.github.io/homelab/posts/nginx-proxy-manager-ssl/</link><pubDate>Sat, 15 Nov 2025 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/nginx-proxy-manager-ssl/</guid><description>&lt;h2 id="the-problem-nginx-proxy-manager-solves"&gt;The Problem Nginx Proxy Manager Solves&lt;/h2&gt;
&lt;p&gt;As your homelab grows, you accumulate services running on various IPs and ports: Proxmox on &lt;code&gt;:8006&lt;/code&gt;, Jellyfin on &lt;code&gt;:8096&lt;/code&gt;, Nextcloud on &lt;code&gt;:443&lt;/code&gt;, Home Assistant on &lt;code&gt;:8123&lt;/code&gt;. Remembering port numbers is tedious, but the bigger issue is HTTPS — browsers complain about self-signed certificates, and accessing services over plain HTTP on your LAN is a security risk.&lt;/p&gt;
&lt;p&gt;Nginx Proxy Manager (NPM) solves both problems. It&amp;rsquo;s a Docker container with a web UI that lets you:&lt;/p&gt;</description></item></channel></rss>