大网数据广告活动
网站运营与故障问答

Reverse proxying a Websocket upstream with Cloudflare

· 52CE 我爱测

I am wanting to use cloudflare on my main website and then use nginx to reverse proxy a directory to my websocket gameserver. NGINX server block : location /Fonzy/ { proxy_pass http://websocket; proxy_http_version 1.1; proxy_set_…

问题原文

原帖链接 · NiCk Newman · CC BY-SA 3.0

I am wanting to use cloudflare on my main website and then use nginx to reverse proxy a directory to my websocket gameserver.

NGINX server block:

    location /Fonzy/ {
                    proxy_pass http://websocket;
                    proxy_http_version 1.1;
                    proxy_set_header Upgrade $http_upgrade;
                    proxy_set_header Connection $connection_upgrade;
        }

Upstream block:

upstream websocket {
        least_conn;
        server GAMESERVERIPHERE:9300;
    }

My question is, since the cloudflare site will be a different server than my gameserver, will the upstream still work? Or does the upstream block server have to be a local address?

The reason why I am curious is because I am wanting the "protection" from cloudflare, but still want to have my gameserver hidden (or should I say reverse proxied).

已采纳解答

原帖链接 · xxdesmus · CC BY-SA 3.0

Currently CloudFlare only allows websocket traffic at the enterprise level. For other plan levels it'll currently be blocked. Eventually websockets will be allowed for all plan levels (likely later this year).

In general, I'd recommend contacting CloudFlare's support team directly. They'd be able to provide the same answer quickly.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2016-01-29)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。