diff --git a/content/Nginx-Proxy-Manager.md b/content/Nginx-Proxy-Manager.md new file mode 100644 index 000000000..1fb4740a4 --- /dev/null +++ b/content/Nginx-Proxy-Manager.md @@ -0,0 +1,26 @@ +--- +title: Nginx proxy manager关于获取ip-ranges.json时卡住的解决方案 +draft: false +date: 2025-01-23 +--- +# 问题描述 +Nginx Proxy manager 默认标准情况下启动时会尝试向[ip-ranges.amazonaws.com](https://ip-ranges.amazonaws.com/ip-ranges.json)获取ip-ranges.json。但是可能由于某种未确定的原因导致程序卡在这一步，日志如下： + + [12/3/2021] [12:48:57 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... + [12/3/2021] [12:48:57 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json + +没有报错，但是又没有进一步的运行报告，显然是卡在这一步了。 + +程序虽然没有报错，由NPM反向代理的网站也可以正常运行，但是NPM的后台无法进入，显示*Bad gateway* 报错。 + +![[Pasted image 20250123114503.png|报错示例]] +*Nginx Proxy Manager报错示例* + +# 解决方案 +解决方案来自[Github上issue的回复](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1405#issuecomment-2376713402) + +``` +NPM_CTR_NAME=nginxproxymanager +docker exec $NPM_CTR_NAME sed -i 's/\.then(internalIpRanges\.fetch)//g' /app/index.js +docker restart $NPM_CTR_NAME +``` diff --git a/content/attachments/Pasted image 20250123114503.png b/content/attachments/Pasted image 20250123114503.png new file mode 100644 index 000000000..9e8532d26 Binary files /dev/null and b/content/attachments/Pasted image 20250123114503.png differ diff --git a/content/index.md b/content/index.md index 34e27dea3..1baf95d9a 100644 --- a/content/index.md +++ b/content/index.md @@ -12,3 +12,5 @@ Nice to meet you! This is Arena speaking. 我以前在想阿巴拉契亚是个什么样子的形象，但是如今认真思考了阿巴拉契亚的历史缘由和发展之后。我认为阿巴拉契亚只要是和阿瑞纳不一样的形象就足以了，无须拘泥于其设定。 # 随笔 1. [[blog-20230310|在国际妇女节的思考——如何解决女性职场不公问题]] +# 运维记录 +1. [[Nginx-Proxy-Manager|Nginx proxy manager关于获取ip-ranges.json时卡住的解决方案]] diff --git a/content/简明管理员手册.md b/content/简明quartz管理员手册.md similarity index 100% rename from content/简明管理员手册.md rename to content/简明quartz管理员手册.md diff --git a/docs/authoring content.md b/docs/authoring content.md index 178f44af8..354f2a904 100644 --- a/docs/authoring content.md +++ b/docs/authoring content.md @@ -2,7 +2,7 @@ title: Authoring Content --- -All of the content in your Quartz should go in the `/content` folder. The content for the home page of your Quartz lives in `content/index.md`. If you've [[index#🪴 Get Started|setup Quartz]] already, this folder should already be initialized. Any Markdown in this folder will get processed by Quartz. +All of the content in your Quartz should go in the `/content` folder. The content for the home page of your Quartz lives in `content/index.md`. If you've [[docs/index#🪴 Get Started|setup Quartz]] already, this folder should already be initialized. Any Markdown in this folder will get processed by Quartz. It is recommended that you use [Obsidian](https://obsidian.md/) as a way to edit and maintain your Quartz. It comes with a nice editor and graphical interface to preview, edit, and link your local files and attachments. diff --git a/docs/build.md b/docs/build.md index 6005770dd..4aa3e5820 100644 --- a/docs/build.md +++ b/docs/build.md @@ -2,7 +2,7 @@ title: "Building your Quartz" --- -Once you've [[index#🪴 Get Started|initialized]] Quartz, let's see what it looks like locally: +Once you've [[docs/index#🪴 Get Started|initialized]] Quartz, let's see what it looks like locally: ```bash npx quartz build --serve diff --git a/docs/setting up your GitHub repository.md b/docs/setting up your GitHub repository.md index 43a556dc1..229554fc7 100644 --- a/docs/setting up your GitHub repository.md +++ b/docs/setting up your GitHub repository.md @@ -2,7 +2,7 @@ title: Setting up your GitHub repository --- -First, make sure you have Quartz [[index#🪴 Get Started|cloned and setup locally]]. +First, make sure you have Quartz [[docs/index#🪴 Get Started|cloned and setup locally]]. Then, create a new repository on GitHub.com. Do **not** initialize the new repository with `README`, license, or `gitignore` files.