Application Name: Snapdrop
Application Site: https://github.com/RobinLinus/snapdrop
Docker Hub: https://hub.docker.com/r/linuxserver/snapdrop/
Github: https://github.com/linuxserver/docker-snapdrop

 

Please post any questions/issues relating to this docker you have in this thread.

If you are not using Unraid (and you should be!) then please do not post here, rather use the linuxserver.io forum for support.

Edited September 24, 20205 yr by linuxserver.io

Superb, thanks! 

Awesome container - is there any plan to add a reverse proxy config file for snapdrop to your swag container? Or, does anybody have a working config they could share? For some reason I'm having problems setting it up despite it being a seemingly simple reverse proxy setup.

the website snapdrop.net works perfectly, but the unraid container won't show other users.

 

I 've changed the normal Port to 4848 (http) 4849 (https)

it sometimes works when I connect from the same Browser and PC

I does not work when I use two different browseres or devices.

 

Any idea where the problem could be?

Edited June 6, 20215 yr by Chaftalie

On 6/6/2021 at 6:05 AM, Chaftalie said:

the website snapdrop.net works perfectly, but the unraid container won't show other users.

 

I 've changed the normal Port to 4848 (http) 4849 (https)

it sometimes works when I connect from the same Browser and PC

I does not work when I use two different browseres or devices.

 

Any idea where the problem could be?

I'm having the same issue. Were you able to solve this?

 

Took the default settings on my network except i gave it it's own ip.

If I open two tabs on the same device, the two clients display each other.

If I open a tab on a pc and an android phone and a tablet, none see each other.  All i get are the following messages in /config/log/nginx/error.log

No network isolation, no guest network I've changing wireless clients to the same vlan.

2021/08/23 01:56:32 [error] 369#369: *120 recv() failed (104: Connection reset by peer) while proxying upgraded connection, client: 192.168.4.36, server: _, request: "GET /server/webrtc HTTP/1.1", upstream: "http://127.0.0.1:3000/server/webrtc", host: "192.168.2.200:8666"


edit: unsure if this makes a difference, if i go to the static http://192.168.2.202:3000/server/webrtc  i get the message "Upgrade Required"

Edited August 24, 20214 yr by linearchaos
more infomation

Works great! Appreciate everything you do for the community linuxserver!

 

Was wondering- is there any way to get this working with SWAG so I can access this container via a subdomain? I tried my hand but unfortunately couldn't get it to work.

 

Thanks!

On 8/23/2021 at 10:03 PM, linearchaos said:

Took the default settings on my network except i gave it it's own ip.

If I open two tabs on the same device, the two clients display each other.

If I open a tab on a pc and an android phone and a tablet, none see each other.  All i get are the following messages in /config/log/nginx/error.log

No network isolation, no guest network I've changing wireless clients to the same vlan.

2021/08/23 01:56:32 [error] 369#369: *120 recv() failed (104: Connection reset by peer) while proxying upgraded connection, client: 192.168.4.36, server: _, request: "GET /server/webrtc HTTP/1.1", upstream: "http://127.0.0.1:3000/server/webrtc", host: "192.168.2.200:8666"


edit: unsure if this makes a difference, if i go to the static http://192.168.2.202:3000/server/webrtc  i get the message "Upgrade Required"

I get the same behavior

 

• Same device appears on both tabs on same PC
• PC to android nothing appears

Sadly it does not work for me either. Devices don’t show up. iPhone, iPad and PC. All using Firefox. Web version works perfectly.

 

I want a refund…. oh…. never mind… 😍

 

Edited December 14, 20214 yr by hernandito
To be funny.

Same behavior here. Gave it a local IP via br0 so I can go directly to IP and page loads but PC Chrome <> Android Chrome no devices appear

2 hours ago, djismgaming said:

Same behavior here. Gave it a local IP via br0 so I can go directly to IP and page loads but PC Chrome <> Android Chrome no devices appear

I resolved this by doing the sed commands noted here inside the container:

https://github.com/RobinLinus/snapdrop/issues/159#issuecomment-691678186

On 12/29/2021 at 5:17 PM, djismgaming said:

I resolved this by doing the sed commands noted here inside the container:

https://github.com/RobinLinus/snapdrop/issues/159#issuecomment-691678186

Tried that and it says directory not available

 

Also trying within LAN

On 4/16/2022 at 5:19 PM, mkono87 said:

Tried that and it says directory not available

 

Also trying within LAN

 

You have to first find where in the container is the referenced file. That is needed since the commands take into consideration that the application is installed on bare hardware and not via the linuxserver image.

 

You can modify the script for your setup like I did.

 

I created snapdrop-single-room.sh inside the /config directory. I created it since it needs to be run (as of now) after every image update.

I commented the original sed lines and added the modifications on lines # START:

 

#!/bin/sh

#sed -i 's/peer.ip/0/g' server/index.js
#sed -i 's/sender.ip/0/g' server/index.js

# make the snapdrop clients be all in a single room

# USE WITH CARE

# Will make it so even local and internet clients see each other
# A literal single room

# USE WITH CARE

# START adjusted for linuxserver/snapdrop docker image
sed -i 's/peer.ip/0/g' /app/snapdrop/server/index.js
sed -i 's/sender.ip/0/g' /app/snapdrop/server/index.js

echo "Please restart container snapdrop"

 

Let us know how it works! Hope it does for you!  

Edited April 26, 20224 yr by djismgaming

Anyone else have any advice on getting this to work? Through a reverse proxy?

Okay, so I managed to get this working. Today I upgraded Snapdrop though and I have no idea what this means I need to do?

 

https://info.linuxserver.io/issues/2022-08-20-nginx-base/

 

Can someone please enlighten me?

 

@blaine07 I dont know what this means. The comment on github issues https://github.com/linuxserver/docker-snapdrop/issues/9#issuecomment-1236914847  thinks this message is clear enough. It looks like there was a push to the docker image a about 6 days ago. I tried removing the app and force updating. I found that changing the Repository to include the latest tag worked.

 

lscr.io/linuxserver/snapdrop:latest

 

saved this change and the new image is working fine. I still dont understand what the original message wants you to do.