From aeb85fc7cc92dd646085cb7f08a9a8d46e0977d0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jirka=20Stehl=C3=ADk?= Date: Tue, 24 Mar 2026 18:44:43 +0100 Subject: [PATCH] Corrected healines --- content/blog/02-hosting-blog.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/blog/02-hosting-blog.md b/content/blog/02-hosting-blog.md index 5204a5c..e2cdaf4 100644 --- a/content/blog/02-hosting-blog.md +++ b/content/blog/02-hosting-blog.md @@ -48,7 +48,7 @@ From this point, I assume that you do have set up domain and DNS to your IPv4 ad Also, I am using VPS with Ubuntu 24, so all commands count with that. -### Set up SSH keys +### Set up SSH This should be your first step. You do not want to enable connection to your VPS just via password. You should generate keys and set up your VPS to accept SSH connection only via them. Good guide how to do from DigitalOcean is [here](https://www.digitalocean.com/community/tutorials/how-to-configure-ssh-key-based-authentication-on-a-linux-server). @@ -80,7 +80,7 @@ ufw delete allow OpenSSH If it doesn't work... well, you have to somehow regain access to your server. You should be able to connect via some kind of console provided by you VPS provider(I cannot really help you with that). And correct your setup. -### Setup WireGuard +### Set up WireGuard WireGuard is our next step. @@ -118,7 +118,7 @@ Now we can enable the network by: systemctl enable --now wg-quick@wg0 ``` -### Setup HAProxy +### Set up HAProxy Now the HAProxy. I think there is good to say a few words why. If we would not set up HAProxy, then from point of view of our home server, all connections would have origin IP of our VPS. We would not be able to check from where did they come from. What HAProxy will do for us is that it will add right origin IP address in front of the requests and Caddy will read it and correctly replace the IP address in the requests.