You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Be able to define specific external ports for the container and have devices be able to see each other when they have navigated to the snapdrop page.
Current Behavior
Have never been able to see another device. I originally pulled this back at the beginning of 2021. The logs below are from the latest container pull after clearing the contents of the '/config' data locally. It doesn't matter if devices are both wired, wireless, or any combination thereof. There is absolutely nothing unusual or unique about the basic home network I'm trying to use this on. As others have noted, I can open a second browser or tab on the same host and see the additional 'device name' there and successfully send a file to the other instance of that device.
Install docker-ce, docker-compose, and all reqs as documented by official docker documentation
Use the compose snippet documented by this repo within its readme.md
Pull image and bring up container
Navigate to the defined http or https port at the external IP of the armv7l device running the container. (In my case this is 192.168.1.2)
snapdrop page should load fine and tell the user what its given "device name" is but no other devices are seen.
Environment
OS: Raspberry Pi OS (uname -a: Linux raspberrypi 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux) CPU architecture: arm32 How docker service was installed: From the official repo, following the official instructions. Currently installed version of docker-ce: 5:20.10.123-0raspbian-buster
Command used to create docker container (run/create/compose/screenshot)
Using the same compose output as described in the readme.md save for my own port mapping:
This is unfortunately one of the limitations of Snapdrop - depending on the setup (local/proxied/internet) you have to make a number of config tweaks to get it working and there's no one size fits all solution we can provide out of the box.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Expected Behavior
Be able to define specific external ports for the container and have devices be able to see each other when they have navigated to the snapdrop page.
Current Behavior
Have never been able to see another device. I originally pulled this back at the beginning of 2021. The logs below are from the latest container pull after clearing the contents of the '/config' data locally. It doesn't matter if devices are both wired, wireless, or any combination thereof. There is absolutely nothing unusual or unique about the basic home network I'm trying to use this on. As others have noted, I can open a second browser or tab on the same host and see the additional 'device name' there and successfully send a file to the other instance of that device.
Also reported in discord here and a few other places: https://discord.com/channels/354974912613449730/506925392603512839/925594810075738134
Steps to Reproduce
Environment
OS: Raspberry Pi OS (uname -a: Linux raspberrypi 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux)
CPU architecture: arm32
How docker service was installed: From the official repo, following the official instructions. Currently installed version of docker-ce: 5:20.10.12
3-0raspbian-busterCommand used to create docker container (run/create/compose/screenshot)
Using the same compose output as described in the readme.md save for my own port mapping:
Docker logs
The text was updated successfully, but these errors were encountered: