nginx 代理 web socket 报错“WebSocket is already in CLO
2020-10-15 19:56
1161 查看
nginx 代理 web socket 报错“WebSocket is already in CLOSING or CLOSED state.”
在生产环境中需要使用 nginx 代理 websocket ，按照正常配置之后发现浏览器一直提示 “WebSocket is already in CLOSING or CLOSED state.”
这是因为 nginx 在代理需要添加如下两个参数
proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade";
加上如下参数正常
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- 问题：Error running 'lugia-web': Address loaclhost:1099 is already in use如下图
- IDEA启动web项目tomcat报错:Error running 'Tomcat': Address localhost:8080 is already in use
- 错误: 代理抛出异常错误: java.rmi.server.ExportException: Port already in use: 1099; nested exception is
- nginx代理WebSocket无法访问ws//WebSocket/xxxx
- 错误: 代理抛出异常错误: java.rmi.server.ExportException: Port already in use: 1099; nested exception is
- Hosting socket.io WebSocket apps in IIS using iisnode
- 解决eclipse中运行web项目时弹出的"Port 8080 required by Tomcat v7.0 Server at localhost is already in use... "
- idea【 Address localhost:1099 is already in use】socket closed
- idea启动web项目报 Error running Tomcat8: Address localhost:1099 is already in use 的错误
- 错误: 代理抛出异常错误: java.rmi.server.ExportException: Port already in use: 1099; nested exception is
- Error running Tomcat8: Address localhost:8080 is already in use 的错误
- mongod 命令执行发现已经有进程在运行mongod数据库--errno:48 Address already in use for socket: 0.0.0.0:27017
- Error response from daemon: Conflict. The container name "/mysql" is already in use by container
- Linux下Socket编程的端口问题( Bind error: Address already in use )
- 轉Linux下 ntp 时间同步服务ntpd 出现 the NTP socket is in use, exiting 解决
- nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
- socket编程注意的地方---bind socket error: Address already in use
- nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)问题的解决
- 解决tomcat端口被占用：Port 8005 required by Tomcat v7.0 Server at localhost is already in use
- Homebrew error: Another active Homebrew process is already in progress