From 0c9a37678f058ce6eeefe6c9ff911e3e6439a59a Mon Sep 17 00:00:00 2001 From: CrimsonTome Date: Thu, 9 Jun 2022 15:50:06 +0000 Subject: [PATCH] fixes --- posts/locking-sites-with-nginx-proxy-manager.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/posts/locking-sites-with-nginx-proxy-manager.md b/posts/locking-sites-with-nginx-proxy-manager.md index 05b47d4..722069d 100644 --- a/posts/locking-sites-with-nginx-proxy-manager.md +++ b/posts/locking-sites-with-nginx-proxy-manager.md @@ -7,7 +7,8 @@ tags: - self-hsting - how-to layout: layouts/post.njk --- +--- + I was looking for a way to lock my sites that need some sort of authentication that does not come built in. I had tried [Autheila](https://github.com/authelia/authelia) but I could never get it working. So here is a quick tutorial on locking sites with [Nginx Proxy Manager](https://nginxproxymanager.com/) (NPM) First of all, I'm going to assume you have some sites that are *already* proxied via NPM. If you don't have any sites proxied then you can folloew [this guide](https://docs.kieranrobson.com/posts/how-to-setup-nginx-proxy-manager-and-cloudflare-copy/) by Kieran Robson. Once you have a site proxied go to your Access Lists, click on Add Access List and give it a name. Under Authorization enter in a username and password you want to lock a site with. Then in Access type all in allow, or if you have a specific IP range you want to be able to connect from, you can enter it here. Leave deny on all then press Save.