這個論壇里面能翻出來的方法已全都測試過，包括百度和必應(yīng)搜出來的結(jié)果，基本上都測試過了，還是沒有找到結(jié)果

[root@ecs-e968-0426361 eleserver]# ulimit -n
102400
[root@ecs-e968-0426361 eleserver]#

看下對應(yīng)的nginx錯誤日志

2025/02/21 02:00:58 [notice] 24832#0: signal process started
2025/02/21 02:14:08 [notice] 25872#0: signal process started
2025/02/21 02:14:12 [notice] 25896#0: signal process started
2025/02/21 02:21:50 [notice] 26590#0: signal process started
2025/02/21 02:21:51 [notice] 26611#0: signal process started
2025/02/21 02:21:51 [notice] 26631#0: signal process started
2025/02/21 02:21:51 [notice] 26650#0: signal process started
2025/02/21 02:21:52 [notice] 26669#0: signal process started
2025/02/21 02:22:02 [notice] 26699#0: signal process started
2025/02/21 02:22:12 [notice] 26726#0: signal process started
2025/02/21 02:22:14 [notice] 26746#0: signal process started
2025/02/21 02:27:30 [notice] 27255#0: signal process started
2025/02/21 02:27:31 [notice] 27279#0: signal process started
2025/02/21 02:27:31 [notice] 27298#0: signal process started
2025/02/21 02:27:32 [notice] 27318#0: signal process started
2025/02/21 02:27:32 [notice] 27337#0: signal process started
2025/02/21 02:27:32 [notice] 27356#0: signal process started
2025/02/21 02:27:56 [notice] 27419#0: signal process started
2025/02/21 02:31:57 [emerg] 27846#0: "proxy_buffer_size" directive is duplicate in /www/server/nginx/conf/nginx.conf:39
2025/02/21 02:32:08 [emerg] 27881#0: "proxy_buffers" directive is duplicate in /www/server/nginx/conf/nginx.conf:39
2025/02/21 02:32:10 [emerg] 27897#0: "proxy_busy_buffers_size" directive is duplicate in /www/server/nginx/conf/nginx.conf:39
2025/02/21 02:32:13 [notice] 27912#0: signal process started
2025/02/21 02:46:03 [notice] 30734#0: signal process started
2025/02/21 02:46:06 [notice] 30755#0: signal process started
2025/02/21 02:46:06 [notice] 30774#0: signal process started
2025/02/21 02:46:33 [emerg] 30817#0: invalid parameter "https2" in /www/server/panel/vhost/nginx/eleapi.fediot.net.conf:8
2025/02/21 02:46:38 [notice] 30835#0: signal process started
2025/02/21 02:46:38 [notice] 30854#0: signal process started
2025/02/21 02:47:10 [notice] 30908#0: signal process started
2025/02/21 02:51:07 [notice] 31323#0: signal process started
2025/02/21 02:52:48 [notice] 31509#0: signal process started
2025/02/21 02:52:51 [notice] 31532#0: signal process started
2025/02/21 02:52:51 [notice] 31550#0: signal process started
2025/02/21 03:14:05 [notice] 923#0: signal process started

大概率是nginx沒啟用keepalive導(dǎo)致的。
http://www.wtbis.cn/doc/webman/others/nginx-proxy.html
這里有nginx配置教程，你參考下，主要是那個keepalive要有

配置的時候完全按照您的官網(wǎng)文檔來設(shè)置的，keepalive 10240 這個設(shè)置項是有的，設(shè)置在upstream xxx里面

nginx好像沒用https2這個參數(shù)

那是我在網(wǎng)上搜的方案，說去掉http2，我就試了一下，發(fā)現(xiàn)不行，我就加回來，手一抖多打了一個s，發(fā)現(xiàn)保存不了我就改回去了，nginx記錄下了這個錯誤。

查看一下nginx的error日志,看是不是臨時目錄權(quán)限問題

權(quán)限直接在項目根目錄給了root 777

是nginx的臨時目錄權(quán)限,不是項目的權(quán)限,開nginx的錯誤日志然后重啟nginx,
一般你這種吊詭的問題很大原因是因為nginx的指定用戶跟命令行運行的用戶不一致導(dǎo)致臨時目錄無法訪問而出錯

先開nginx的error日志吧,出錯了里面應(yīng)該有詳細(xì)的報錯信息

如果錯誤日志里有Permission Denied的報錯,大概率就是nginx的臨時目錄權(quán)限