部署到服务器后，使用nginx端口转发后发现所有的按钮全都链接超时了 #155

Week888 · 2023-03-30T08:47:32Z

已经通过DNS解析将<域名>解析到服务器IP上
只是通过nginx简单的把80端口的请求转发到了这个python工程启动设置的端口（5566）上。
在浏览器输入<域名>可以访问主页面，但发现点击任何按钮都是超时的。
如果在浏览器内输入域名：5566则一切正常。

nginx配置如下图

请有经验的朋友帮下忙感谢！

knigth95 · 2023-03-30T09:02:35Z

想问一下，如何使用ip访问，后台nohup挂起后无法在控制台获取公用url的域名地址，使用ip端口进入链接超时

Week888 · 2023-03-30T09:06:11Z

想问一下，如何使用ip访问，后台nohup挂起后无法在控制台获取公用url的域名地址，使用ip端口进入链接超时

没有听懂，运行后直接用ip访问就行

knigth95 · 2023-03-30T09:30:18Z

想问一下，如何使用ip访问，后台nohup挂起后无法在控制台获取公用url的域名地址，使用ip端口进入链接超时

没有听懂，运行后直接用ip访问就行

可能是我服务器端口出了问题，我设置的端口无法访问，现在可以访问了，但是提交东西会显示error

mengfanjie95 · 2023-03-30T09:47:28Z

你好，请问问题解决了吗，我也是用的nginx代理，也是可以打开界面但是使用具体功能的时候报错error，另一个gradio的地址就可以正常使用

Week888 · 2023-03-30T09:50:02Z

解决了，需要为 websocket配置参数

binary-husky · 2023-03-30T11:21:07Z

和websocket有关吧

colin4k · 2023-03-31T01:49:04Z

发现只要设置密码，局域网访问就会connection error，

tanghcn · 2023-03-31T08:46:14Z

发现只要设置密码，局域网访问就会connection error，
我测试也遇到这个情况

RexWzh · 2023-04-01T12:52:13Z

解决了，需要为 websocket配置参数

尝试了官方 wiki 的这个，没有成功。。。请问你这段代码是在哪里找到（试了好像也没效果

map $http_upgrade $connection_upgrade {
	default upgrade;
	'' close;
}

upstream my_chataca {
	server 127.0.0.1:<端口>;
}

server {
	listen 80;
	listen [::]:80;
	server_name <域名>;

	location / {
		proxy_pass http://my_chataca;
		proxy_set_header Host $host;
		proxy_set_header X-Real-IP $remote_addr;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection $connection_upgrade;
	}
}

RexWzh · 2023-04-01T14:18:31Z

个人在韩区服务器部署的服务，直接用 git clone 部署，目前情况：

不设置密码，只用 IP/域名 + 端口能够访问
设置密码，IP + 端口也不能访问

不设置密码/设置密码，域名 + 重定向访问不了，尝试了下方配置

map $http_upgrade $connection_upgrade {
    default keep-alive;
    '' upgrade;
}

server {
    listen 80;
    listen [::]:80;
    server_name <域名>;

    location / {
	    proxy_pass http://localhost:2333/;
	    proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
	    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
	    proxy_set_header Upgrade $http_upgrade;
	    proxy_set_header Connection $connection_upgrade;
    }
}

问题应该有两个：重定向问题和密码问题。

ATPs · 2023-04-01T15:49:57Z

同样没有成功。

ATPs · 2023-04-02T02:04:57Z

终于成功部署了。

像上面写的：

nginx 配置
在/etc/nginx/conf.d 文件夹里，新建一个文件，例如
your_domain_url.conf的文件。your_domain_url就是你的域名，可以是二级域名。如：happy.ppimage.net

内容为：

server {
        listen 80;
        server_name your_domain_url;   # 请填入你设定的域名
        access_log off;
        error_log off;
        location / {
                proxy_pass http://127.0.0.1:8001;   # 注意端口号
                proxy_redirect off;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header Upgrade $http_upgrade;         # Websocket配置
                proxy_set_header Connection $connection_upgrade;                #Websocket配置
                proxy_max_temp_file_size 0;
                client_max_body_size 10m;
                client_body_buffer_size 128k;
                proxy_connect_timeout 90;
                proxy_send_timeout 90;
                proxy_read_timeout 90;
                proxy_buffer_size 4k;
                proxy_buffers 4 32k;
                proxy_busy_buffers_size 64k;
                proxy_temp_file_write_size 64k;
        }
}

在上级目录里编辑 /etc/nginx/nginx.conf,配置类似

user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

# Load dynamic modules. See /usr/share/doc/nginx/README.dynamic.
include /usr/share/nginx/modules/*.conf;

events {
    worker_connections 1024;
}

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;
    server_tokens off;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 2048;
    gzip                on;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    # Load modular configuration files from the /etc/nginx/conf.d directory.
    # See http://nginx.org/en/docs/ngx_core_module.html#include
    # for more information.
    include /etc/nginx/conf.d/*.conf;

    map $http_upgrade $connection_upgrade {
        default upgrade;
        '' close;
    }

}

主要是添加了

    map $http_upgrade $connection_upgrade {
        default upgrade;
        '' close;
    }

然后就可以通过域名访问了。注意，这里端口是80，不是443.

我是域名用cloudflare解析的。

没有开启ssl.

这里有教程

https://defunctions.com/cdn/http_to_https_by_cf.html

可以“使用CloudFlare将不配置SSL的http源站转换成https”

z727354123 · 2023-04-02T17:10:15Z

个人在韩区服务器部署的服务，直接用 git clone 部署，目前情况：
不设置密码，只用 IP/域名 + 端口能够访问

设置密码，IP + 端口也不能访问
不设置密码/设置密码，域名 + 重定向访问不了，尝试了下方配置
map $http_upgrade $connection_upgrade {
    default keep-alive;
    '' upgrade;
}

server {
    listen 80;
    listen [::]:80;
    server_name <域名>;

    location / {
	    proxy_pass http://localhost:2333/;
	    proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
	    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
	    proxy_set_header Upgrade $http_upgrade;
	    proxy_set_header Connection $connection_upgrade;
    }
}
问题应该有两个：重定向问题和密码问题。

-- 密码问题应该是 gradio 在 http 下 ws 问题, 加了证书变成 wss 应该没事,
gradio-issues

-- 我修改了 routes.py 就好了, docker 我不是很熟, 粗略修改, 但是对我有效

进入容器

docker exec -it xxx /bin/bash

修改文件 routes.py

sed -i s/websocket\.cookies\.get\(\"access-token\"\)/websocket.cookies.get\(\"access-token-unsecure\"\)/g  /usr/local/lib/python3.11/site-packages/gradio/routes.py

重启容器

docker restart xxx

gptbert · 2023-04-03T03:20:32Z

#155 (comment)

使用CloudFlare将不配置SSL的http源站转换成https，按照这个方法搞定了，非常感谢！

blacksino · 2023-05-10T08:12:19Z

你好，我在本地运行了两个带密码的webui的实例，分别运行在7861和7862，现在我想通过nginx实现负载均衡，发现无法登陆，以下是我nginx的配置文件：

http {

    upstream backend
    {
        server localhost:7861;
        server localhost:7862;
     }
    server
    {
        listen 80;
        server_name localhost;
        location / {
            proxy_pass http://backend;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header Upgrade $http_upgrade;         # Websocket配置
            proxy_set_header Connection $connection_upgrade;

     }
    }
    map $http_upgrade $connection_upgrade
    {
        default upgrade;
        '' close;
    }
}

，而nginx错误日志是：

2023/05/10 16:04:46 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7862/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:04:58 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7861/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:04:58 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7862/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:05:00 [error] 22657#22657: *221 no live upstreams while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://backend/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:05:03 [error] 22657#22657: *221 no live upstreams while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://backend/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:05:09 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7861/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:05:23 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7861/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"

请问各位大佬如何解决？

jasonliu222 · 2023-12-27T06:42:17Z

已经通过DNS解析将<域名>解析到服务器IP上只是通过nginx简单的把80端口的请求转发到了这个python工程启动设置的端口（5566）上。在浏览器输入<域名>可以访问主页面，但发现点击任何按钮都是超时的。如果在浏览器内输入域名：5566则一切正常。

nginx配置如下图

请有经验的朋友帮下忙感谢！

你用了反代，填的通道就不是你的宿主机IP了，直接用http://127.0.0.1:8001; # 注意端口号
或者localhost就行

jasonliu222 · 2023-12-27T06:45:39Z

你好，我在本地运行了两个带密码的webui的实例，分别运行在7861和7862，现在我想通过nginx实现负载均衡，发现无法登陆，以下是我nginx的配置文件：

http {

    upstream backend
    {
        server localhost:7861;
        server localhost:7862;
     }
    server
    {
        listen 80;
        server_name localhost;
        location / {
            proxy_pass http://backend;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header Upgrade $http_upgrade;         # Websocket配置
            proxy_set_header Connection $connection_upgrade;

     }
    }
    map $http_upgrade $connection_upgrade
    {
        default upgrade;
        '' close;
    }
}

，而nginx错误日志是：

2023/05/10 16:04:46 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7862/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:04:58 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7861/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:04:58 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7862/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:05:00 [error] 22657#22657: *221 no live upstreams while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://backend/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:05:03 [error] 22657#22657: *221 no live upstreams while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://backend/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:05:09 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7861/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"
2023/05/10 16:05:23 [error] 22657#22657: *221 connect() failed (111: Connection refused) while connecting to upstream, client: 10.190.67.97, server: localhost, request: "POST /internal/progress HTTP/1.1", upstream: "http://127.0.0.1:7861/internal/progress", host: "10.12.43.140:8080", referrer: "http://10.12.43.140:8080/?__theme=dark"

请问各位大佬如何解决？

看报错像是防火墙没开

xwj216 · 2024-05-20T07:11:08Z

找不到任何.tex文件: private_upload/helede/2024-05-20-05-01-40
上传文件优化时，出现这种提示，明明路径下有上传的文件呢

binary-husky mentioned this issue Mar 30, 2023

设置密码后遇到Connection errored out #167

Closed

gptbert mentioned this issue Apr 3, 2023

[BUG/Help] 我可以使用我自己的公网ip吗 THUDM/ChatGLM-6B#341

Closed

1 task

NeoDH mentioned this issue Apr 4, 2023

阿里云服务器部署到公网访问 #203

Closed

binary-husky closed this as completed Apr 12, 2023

mengxiangbao mentioned this issue May 11, 2023

在群晖ds220+上部署了该项目，通过本地局域网IP:端口号，可以正常访问；通过设置的https域名，能打开登录页面，也能正常登录，但提交问题的时候出错，该怎么处理。 #730

Closed

binaryYuki mentioned this issue May 8, 2024

[Bug]: centos上docker-compose部署后无法使用 #1770

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

部署到服务器后，使用nginx端口转发后发现所有的按钮全都链接超时了 #155

部署到服务器后，使用nginx端口转发后发现所有的按钮全都链接超时了 #155

Week888 commented Mar 30, 2023

knigth95 commented Mar 30, 2023

Week888 commented Mar 30, 2023

knigth95 commented Mar 30, 2023

mengfanjie95 commented Mar 30, 2023

Week888 commented Mar 30, 2023

binary-husky commented Mar 30, 2023

colin4k commented Mar 31, 2023

tanghcn commented Mar 31, 2023

RexWzh commented Apr 1, 2023

RexWzh commented Apr 1, 2023 •

edited

Loading

ATPs commented Apr 1, 2023

ATPs commented Apr 2, 2023

z727354123 commented Apr 2, 2023

gptbert commented Apr 3, 2023 •

edited

Loading

blacksino commented May 10, 2023 •

edited

Loading

jasonliu222 commented Dec 27, 2023

jasonliu222 commented Dec 27, 2023

xwj216 commented May 20, 2024

部署到服务器后，使用nginx端口转发后发现所有的按钮全都链接超时了 #155

部署到服务器后，使用nginx端口转发后发现所有的按钮全都链接超时了 #155

Comments

Week888 commented Mar 30, 2023

knigth95 commented Mar 30, 2023

Week888 commented Mar 30, 2023

knigth95 commented Mar 30, 2023

mengfanjie95 commented Mar 30, 2023

Week888 commented Mar 30, 2023

binary-husky commented Mar 30, 2023

colin4k commented Mar 31, 2023

tanghcn commented Mar 31, 2023

RexWzh commented Apr 1, 2023

RexWzh commented Apr 1, 2023 • edited Loading

ATPs commented Apr 1, 2023

ATPs commented Apr 2, 2023

z727354123 commented Apr 2, 2023

gptbert commented Apr 3, 2023 • edited Loading

blacksino commented May 10, 2023 • edited Loading

jasonliu222 commented Dec 27, 2023

jasonliu222 commented Dec 27, 2023

xwj216 commented May 20, 2024

RexWzh commented Apr 1, 2023 •

edited

Loading

gptbert commented Apr 3, 2023 •

edited

Loading

blacksino commented May 10, 2023 •

edited

Loading