snapdrop icon indicating copy to clipboard operation
snapdrop copied to clipboard

connection lost. try in 5 seconds

Open RobsonKazu opened this issue 2 years ago • 7 comments

connection lost. try in 5 seconds it is happening frequently

Captura de tela 2022-08-11 153952

RobsonKazu avatar Aug 11 '22 18:08 RobsonKazu

Please just pull the docker image from docker hub and run it,don't use the docker-compose

Corpama avatar Aug 17 '22 06:08 Corpama

Could you please recheck @RobsonKazu?

Ein-Tim avatar Aug 25 '22 18:08 Ein-Tim

+1 WebSocket connection to 'wss://myurl.com/server/webrtc' failed: WS: server disconnected

wxjer avatar Sep 14 '22 12:09 wxjer

resloved, add this header to nginx agent: proxy_set_header Connection "upgrade"; proxy_set_header Upgrade $http_upgrade; proxy_set_header X-Forwarded-for $remote_addr;

here is the link

wxjer avatar Sep 14 '22 13:09 wxjer

here is the link

Why the nginx config has port 3000? The official docker documentation exposes only port 80 and 443.

I followed the same doc and I'm getting Connection lost error.

Here are my commands:

docker run -d \
  --name=snapdrop \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Asia/Dubai\
  -p 127.0.0.1:44500:80 \
  -p 127.0.0.1:44511:443 \
  -v /opt/snapdrop:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/snapdrop:latest

My nginx config:

server {

    listen 80;
    server_name snap.example.com;
    return 301 https://$host$request_uri;
}

server {

    listen 443 ssl http2;
    server_name snap.example.com;

    ssl_certificate /etc/letsencrypt/live/snap.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/snap.example.com/privkey.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/snap.example.com/chain.pem;

    add_header X-XSS-Protection          "1; mode=block" always;
    add_header X-Content-Type-Options    "nosniff" always;

    location ~ /\.(?!well-known) {
      deny all;
      access_log off;
    }
    
    # reverse proxy
    location / {
      proxy_pass https://127.0.0.1:44511/;
      proxy_set_header Connection "upgrade";
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header X-Forwarded-for $remote_addr;
      proxy_set_header  X-Real-IP $remote_addr;
    }

}

What am I doing wrong? @wxjer @RobsonKazu @Corpama

hexclann avatar Nov 02 '22 10:11 hexclann

I still cannot get it to work. <ip-addr:port> works on HTTP, however, a reverse proxy with Nginx does not work. Any other hint?

location /server {
	proxy_connect_timeout 300;
	proxy_pass http//127.0.0.1:8085;
	proxy_set_header Connection "upgrade";
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header X-Forwarded-for $remote_addr;
}

glimz avatar Aug 08 '23 16:08 glimz

Using docker image resolves this problem for me but adding header doesn't.

Please just pull the docker image from docker hub and run it,don't use the docker-compose

resloved, add this header to nginx agent: proxy_set_header Connection "upgrade"; proxy_set_header Upgrade $http_upgrade; proxy_set_header X-Forwarded-for $remote_addr;

here is the link

Jay54520 avatar Oct 14 '23 05:10 Jay54520