NPM won't detect Netbird container after restart

未关闭
#5,653 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
技术栈
docker, nginx, typescript

调研方向

通过在 NetBird 之前启动 Nginx Proxy Manager,或重启 NetBird,来复现该故障,然后检查引用 /data/nginx/proxy_host/yy.conf 的 nginx 错误。在 Nginx Proxy Manager v2.15.1 和 Ubuntu 24.04 上验证该行为。当 netbird-server 重启后代理能够恢复,且无需手动重启 NPM 时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

bug

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes / No
  • Are you sure you're not using someone else's docker image?
    • Yes / No
  • Have you searched for similar issues (both open and closed)?
    • Yes / No

Describe the bug

When NPM starts before netbird or when netbird(netbird-server) restarts, NPM keeps spamming cannot find netbird-server upstream. Even though the server is fully restarted and fully active, it still says the same thing.

Nginx Proxy Manager Version
v2.15.1

To Reproduce
Steps to reproduce the behavior:
All the above.
So, setup npm and netbird and then after verifying that everything works normally, restart netbird(server) and wait for npm to say that it cant find upstream.

Expected behavior
Error:
❯ Starting nginx ...
nginx: [emerg] host not found in upstream "netbird-server" in /data/nginx/proxy_host/yy.conf:xx

Operating System

Ubuntu 24.04 x86_64

Additional context
This issue is very annoying as it requires restarting npm to resolve. Sometimes, it even clogs at startup so I cant even access absolutely anything that is behind NPM namely Portainer, ..... .

主要语言
TypeScript
星标
34.2k
派生
3.9k
平均合并
21 小时 12 分钟
30 天内合并 PR
20

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

NginxProxyManager/nginx-proxy-manager 的其他 Issue

查看 NginxProxyManager/nginx-proxy-manager 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。