From b714f3065d49da2c84f36eeb170d434c4fd700cb Mon Sep 17 00:00:00 2001 From: thomas-dagostino Date: Mon, 30 Dec 2024 14:58:15 +0000 Subject: [PATCH] docs: update home/linux/nginx-proxy-manager --- home/linux/nginx-proxy-manager.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/home/linux/nginx-proxy-manager.md b/home/linux/nginx-proxy-manager.md index dfc490e..f942a80 100644 --- a/home/linux/nginx-proxy-manager.md +++ b/home/linux/nginx-proxy-manager.md @@ -2,7 +2,7 @@ title: Nginx Proxy Manager description: A guide to what settings have worked so far, probably because of ignorance ;P published: true -date: 2024-07-04T20:12:06.437Z +date: 2024-12-30T14:58:14.239Z tags: editor: markdown dateCreated: 2024-07-04T20:12:04.709Z @@ -13,4 +13,8 @@ For NPM to work locally without needing public access: * DNS A record pointing npmhostname.localdomain.domain.com to NPM * Host record in NPM pointing host (local)FQDN above to itself * Unifi - add wildcard domain to point to NPM instance - * Potential testing with CNAME records soon \ No newline at end of file + * Potential testing with CNAME records soon + + Alternatively, one could use cloudflare to generate custom API key, + set the key for DNS Zone edit, then copy the key to NPM as DNS challenge to generate wildcard cert. +*Does not require manually adding a record and port forwarding.* \ No newline at end of file