<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>SelfHosting on Esc.sh Archive</title>
		<link>https://archive.esc.sh/tags/selfhosting/</link>
		<description>Recent content in SelfHosting on Esc.sh Archive</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 15 Feb 2026 20:22:18 +0000</lastBuildDate>
		
			<atom:link href="https://archive.esc.sh/tags/selfhosting/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Simple monitoring with Beszel</title>
				<link>https://archive.esc.sh/blog/simple-monitoring-with-beszel/</link>
				<pubDate>Tue, 11 Feb 2025 14:51:24 +0000</pubDate>
				<guid>https://archive.esc.sh/blog/simple-monitoring-with-beszel/</guid>
				<description>&lt;h2 id=&#34;what-is-beszel&#34;&gt;What is Beszel&lt;a class=&#34;anchor&#34; href=&#34;#what-is-beszel&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;It is a lightweight monitoring platform including docker stats, alerts and a web UI. Take a look at the official documentation &lt;a href=&#34;https://beszel.dev/guide/what-is-beszel&#34;&gt;HERE&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-not-grafana--prometheus&#34;&gt;Why not Grafana + Prometheus&lt;a class=&#34;anchor&#34; href=&#34;#why-not-grafana--prometheus&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;If you already have a Grafana + Prometheus stack, you are not missing out on anything. Beszel is a much simpler and lighter alternatives to Grafana+Prometheus. I personally have a full Prometheus + Grafana stack, but I wanted to give Beszel a try and I found it pretty nice.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Fix Synology Docker Containers No  Internet Access</title>
				<link>https://archive.esc.sh/blog/synology-nas-container-no-internet/</link>
				<pubDate>Sun, 09 Feb 2025 17:58:19 +0000</pubDate>
				<guid>https://archive.esc.sh/blog/synology-nas-container-no-internet/</guid>
				<description>&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;a class=&#34;anchor&#34; href=&#34;#the-problem&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;You have started a new container in your Synology NAS using Container Manager, but for some reason it does not have internet access.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-solution&#34;&gt;The Solution&lt;a class=&#34;anchor&#34; href=&#34;#the-solution&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Fortunately, it is very easy to fix. It is most probably due to your Synology&amp;rsquo;s firewall rules. So, all we have to do is add the docker container&amp;rsquo;s IP ranges to the firewall&lt;/p&gt;&#xA;&lt;h3 id=&#34;step-1--find-your-docker-containers-ip-range&#34;&gt;Step 1 : Find your docker container&amp;rsquo;s IP range&lt;a class=&#34;anchor&#34; href=&#34;#step-1--find-your-docker-containers-ip-range&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Open &amp;ldquo;Container Manager&amp;rdquo; and go to your container that is having issues. Go to &lt;code&gt;General&lt;/code&gt; -&amp;gt; &lt;code&gt;Network&lt;/code&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Setting up Prometheus and Grafana using Docker</title>
				<link>https://archive.esc.sh/blog/prometheus-grafana/</link>
				<pubDate>Wed, 05 Feb 2025 04:47:29 +0000</pubDate>
				<guid>https://archive.esc.sh/blog/prometheus-grafana/</guid>
				<description>&lt;p&gt;Prometheus and Grafana for Homelab monitoring is not as difficult as you think. It literally takes 10 minutes to get everything up&lt;/p&gt;&#xA;&lt;p&gt;If you want to try something slightly simpler, you can give Beszel a try too. Check it out &lt;a href=&#34;https://archive.esc.sh/blog/simple-monitoring-with-beszel/&#34;&gt;Simple monitoring with Beszel&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;requirements&#34;&gt;Requirements&lt;a class=&#34;anchor&#34; href=&#34;#requirements&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A Linux Machine / VM with Docker installed. If you do not have docker installed, you can follow &lt;a href=&#34;https://archive.esc.sh/blog/debian-quick-docker-installation/&#34;&gt;this&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;architecture&#34;&gt;Architecture&lt;a class=&#34;anchor&#34; href=&#34;#architecture&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Before we set it up, I think it makes sense to get an idea of how everything fits together. If you are already familiar with Grafana/Prometheus, feel free to skip this part&lt;/p&gt;</description>
			</item>
			<item>
				<title>Traefik Reverse Proxy with Docker</title>
				<link>https://archive.esc.sh/blog/traefik-docker/</link>
				<pubDate>Fri, 03 Jan 2025 22:24:07 +0000</pubDate>
				<guid>https://archive.esc.sh/blog/traefik-docker/</guid>
				<description>&lt;p&gt;In this article, I will show you how to have a fully functioning self hosting environment with Docker and Traefik as the reverse proxy.&lt;/p&gt;&#xA;&lt;h2 id=&#34;whats-covered&#34;&gt;What&amp;rsquo;s covered&lt;a class=&#34;anchor&#34; href=&#34;#whats-covered&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Docker to run everything (Using Docker compose)&lt;/li&gt;&#xA;&lt;li&gt;Traefik as a &lt;strong&gt;single reverse proxy for all services&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;Automatic port discovery (no more exposing or having to remember ports)&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;No more port collision&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Automatic TLS/SSL for all services (&lt;strong&gt;including local domains&lt;/strong&gt;)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;some-backstory&#34;&gt;Some backstory&lt;a class=&#34;anchor&#34; href=&#34;#some-backstory&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;I have been using Nginx Proxy Manager as the reverse proxy for my self hosting setup. While this worked out great, there was no native docker integration. What do I mean by that? Well, if you use a single host to run a bunch of docker containers, &lt;strong&gt;you will have to keep track of the port numbers&lt;/strong&gt;, configure them in the Nginx Proxy Manager manually and &lt;strong&gt;make sure that ports don&amp;rsquo;t clash&lt;/strong&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Setting up Wireguard VPN</title>
				<link>https://archive.esc.sh/blog/wireguard-vpn-setup/</link>
				<pubDate>Mon, 01 Jan 2024 19:20:00 +0000</pubDate>
				<guid>https://archive.esc.sh/blog/wireguard-vpn-setup/</guid>
				<description>&lt;p&gt;In this post, I will show you how we can connect two peers (any two servers/instances) via Wireguard.&#xA;As long as at least one of the peer is able to connect directly to the other one, this should work&#xA;even if one of the peer is behind a NAT/firewall that blocks incoming connections.&lt;/p&gt;&#xA;&lt;p&gt;For this demonstration, I will connect a local Virtual Machine to a remote Cloud VM via Wireguard.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Let&#39;s Encrypt &#43; Nginx - Definitive Guide for SSL (Production Ready)</title>
				<link>https://archive.esc.sh/blog/lets-encrypt-and-nginx-definitive-guide/</link>
				<pubDate>Sun, 27 Sep 2020 19:14:00 +0000</pubDate>
				<guid>https://archive.esc.sh/blog/lets-encrypt-and-nginx-definitive-guide/</guid>
				<description>&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;Feb 2026 Update&lt;/strong&gt;: The post has been updated to account for recent changes to certbot such as systemd timer for renewal&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;This blog post explains how to setup and configure SSL for a domain name&lt;br&gt;&#xA;with Let&amp;rsquo;s Encrypt and Nginx&lt;/p&gt;&#xA;&lt;p&gt;This should work for any Debian-based distro (Debian 12/13+, Ubuntu 22.04+, etc.)&lt;/p&gt;&#xA;&lt;h2 id=&#34;goals&#34;&gt;Goals&lt;a class=&#34;anchor&#34; href=&#34;#goals&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Fetch SSL certificates for a domain&lt;/li&gt;&#xA;&lt;li&gt;Configure Nginx to use SSL&lt;/li&gt;&#xA;&lt;li&gt;HTTP to HTTPS redirection&lt;/li&gt;&#xA;&lt;li&gt;Auto renew certificates&lt;/li&gt;&#xA;&lt;li&gt;Redirect www to non-www or viceversa&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Redirect www to non-www without http to https redirection&lt;/li&gt;&#xA;&lt;li&gt;Redirect www to non-www with http to https redirection&lt;/li&gt;&#xA;&lt;li&gt;Redirect non-www to www without http to https redirection&lt;/li&gt;&#xA;&lt;li&gt;Redirect non-www to www with http to https redirection&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;a class=&#34;anchor&#34; href=&#34;#prerequisites&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;A publicly accessible server (if you plan to use HTTP challenge to fetch the certificate)&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
