خرید بک لینک

Vote count: 0

server {

listen 80;
listen 443 default_server ssl;
root /usr/share/nginx/html;
index index.html index.htm;


server_name budokai-online.com;

ssl off;
ssl_certificate      /etc/ssl/budokai-online_com.crt;
ssl_certificate_key  /etc/ssl/budokai-online_com.key;

if ($ssl_protocol = "") {
rewrite ^ https://$host$request_uri? permanent;
} 
location / {
#Backend Sinatra-Websockets
  proxyhttpversion 1.1;
  proxypass http://budokai-online.com:8080;
  proxysetheader X-Real-IP $remoteaddr;
  proxysetheader Host $host;
  proxysetheader X-Forwarded-For $proxyaddxforwardedfor;
  proxysetheader XFORWARDEDPROTO https;

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Coection "Upgrade";
proxy_set_header Sec-WebSocket-Key $http_sec_websocket_key;
proxy_read_timeout 86400;
# add_header    Sec-WebSocket-Protocol  'v10.stomp, v11.stomp';
}

My team is having an issue where our website's websockets are coecting some people to our website just fine, but others can't. When they login they get a coection ended error but others get no error at all. We thought it was a bandwidth/data issue, but we aren't completely sure, so we plan on using a fallback until we get a solution. Can anyone help with a solution for this? We're using Linux, sintra websockets and Nginx. Sever setup.

Also some interesting notes that it works on Chrome and Oprah on my computer but not Firefox.

Error I could grab. Firefox can’t establish a coection to the server at wss://budokai-online.com/arena.

ws = new WebSocket('wss://budokai-online.com/arena');

Tested on all broswers.

asked 33 secs ago

برچسب: نویسنده: استخدام کار تاريخ: پنجشنبه 8 مهر 1395 ساعت: 20:17

صفحه بندی