[GH-ISSUE #829] live接口和enabled接口返回404 #4870

Closed
opened 2026-03-01 15:36:52 +03:00 by kerem · 15 comments
Owner

Originally created by @liuhd92 on GitHub (Jan 23, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/829

/api/notifications/live这个接口和/api/environments/enabled这个接口,一直报404,现在出现一个问题,那就是无法申请ssl证书,应该和这两个接口报404有关系,一直卡在0%的位置

Image

就一直卡在这,其他的接口都没问题,正常200

Originally created by @liuhd92 on GitHub (Jan 23, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/829 /api/notifications/live这个接口和/api/environments/enabled这个接口,一直报404,现在出现一个问题,那就是无法申请ssl证书,应该和这两个接口报404有关系,一直卡在0%的位置 <img width="1772" alt="Image" src="https://github.com/user-attachments/assets/04be0888-0465-4337-bf00-8b47b350bf5f" /> 就一直卡在这,其他的接口都没问题,正常200
kerem 2026-03-01 15:36:52 +03:00
Author
Owner

@0xJacky commented on GitHub (Jan 23, 2025):

您好,申请证书接口跟这个没有关系。你看一下websocket 代理配置了没有。

<!-- gh-comment-id:2609806334 --> @0xJacky commented on GitHub (Jan 23, 2025): 您好,申请证书接口跟这个没有关系。你看一下websocket 代理配置了没有。
Author
Owner

@0xJacky commented on GitHub (Jan 23, 2025):

sse 的接口按理说不应该报404的,你的 nginx 配置文件可以贴出来看一下吗?

<!-- gh-comment-id:2609809687 --> @0xJacky commented on GitHub (Jan 23, 2025): sse 的接口按理说不应该报404的,你的 nginx 配置文件可以贴出来看一下吗?
Author
Owner

@0xJacky commented on GitHub (Jan 24, 2025):

你是在使用的子目录部署方式吗

<!-- gh-comment-id:2611976161 --> @0xJacky commented on GitHub (Jan 24, 2025): 你是在使用的子目录部署方式吗
Author
Owner

@liuhd92 commented on GitHub (Feb 7, 2025):

Image这事单个项目的配置

<!-- gh-comment-id:2642410818 --> @liuhd92 commented on GitHub (Feb 7, 2025): <img width="784" alt="Image" src="https://github.com/user-attachments/assets/e7a0eb3d-8078-4fb9-b94b-95c76a2391f5" />这事单个项目的配置
Author
Owner

@0xJacky commented on GitHub (Feb 7, 2025):

更新一下最新版本,应该修复了

<!-- gh-comment-id:2642450813 --> @0xJacky commented on GitHub (Feb 7, 2025): 更新一下最新版本,应该修复了
Author
Owner

@liuhd92 commented on GitHub (Feb 7, 2025):

Image升级也卡主 - -

<!-- gh-comment-id:2642479708 --> @liuhd92 commented on GitHub (Feb 7, 2025): <img width="1749" alt="Image" src="https://github.com/user-attachments/assets/6810bb15-e85d-423a-8894-728a354f254b" />升级也卡主 - -
Author
Owner

@0xJacky commented on GitHub (Feb 7, 2025):

用脚本更新吧,GitHub被墙了

<!-- gh-comment-id:2642485829 --> @0xJacky commented on GitHub (Feb 7, 2025): 用脚本更新吧,GitHub被墙了
Author
Owner

@0xJacky commented on GitHub (Feb 7, 2025):

更新完看一下 系统 > 自我检查

<!-- gh-comment-id:2642487424 --> @0xJacky commented on GitHub (Feb 7, 2025): 更新完看一下 系统 > 自我检查
Author
Owner

@liuhd92 commented on GitHub (Feb 7, 2025):

Image 确实不报错了,但是申请证书的时候还是卡主,我也按照说明中修改了
<!-- gh-comment-id:2642509466 --> @liuhd92 commented on GitHub (Feb 7, 2025): <img width="1210" alt="Image" src="https://github.com/user-attachments/assets/27e29fd1-f644-4ebb-903f-36f2543069f4" /> 确实不报错了,但是申请证书的时候还是卡主,我也按照说明中修改了
Author
Owner

@liuhd92 commented on GitHub (Feb 7, 2025):

确实是反向代理了nginxui,我的配置如下,标红的是nginx-ui的配置,是有什么问题吗

Image
<!-- gh-comment-id:2642519262 --> @liuhd92 commented on GitHub (Feb 7, 2025): 确实是反向代理了nginxui,我的配置如下,标红的是nginx-ui的配置,是有什么问题吗 <img width="738" alt="Image" src="https://github.com/user-attachments/assets/990eabb5-8a61-4134-b728-241c0636fb1d" />
Author
Owner

@0xJacky commented on GitHub (Feb 7, 2025):

这个看起来是子目录部署的bug,可以看一下F12 网络请求 ws 分类吗

<!-- gh-comment-id:2642534618 --> @0xJacky commented on GitHub (Feb 7, 2025): 这个看起来是子目录部署的bug,可以看一下F12 网络请求 ws 分类吗
Author
Owner

@0xJacky commented on GitHub (Feb 7, 2025):

不对,你是不是漏给 /nginxui/ 配置了 Upgrade和 Connection的 proxy header

<!-- gh-comment-id:2642538322 --> @0xJacky commented on GitHub (Feb 7, 2025): 不对,你是不是漏给 /nginxui/ 配置了 Upgrade和 Connection的 proxy header
Author
Owner

@liuhd92 commented on GitHub (Feb 7, 2025):

对对对,是的是的,真是一句惊醒梦中人啊,膜拜!!!

<!-- gh-comment-id:2642555259 --> @liuhd92 commented on GitHub (Feb 7, 2025): 对对对,是的是的,真是一句惊醒梦中人啊,膜拜!!!
Author
Owner

@liuhd92 commented on GitHub (Feb 7, 2025):

搞定了已经

<!-- gh-comment-id:2642555450 --> @liuhd92 commented on GitHub (Feb 7, 2025): 搞定了已经
Author
Owner

@0xJacky commented on GitHub (Feb 7, 2025):

搞定了已经

<!-- gh-comment-id:2642570292 --> @0xJacky commented on GitHub (Feb 7, 2025): > 搞定了已经 嗯
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-ui#4870
No description provided.