snapdrop
snapdrop copied to clipboard
Can't get it to work between iOS and MacOS
Can't get this to work between iOS and MacOS. I can get it to work between two Mac computers, but not between iOS and a Mac. I believe the issue is with the iOS implementation. Using Firefox on both devices. iOS 16.1.1
Do you have iCloud+ and activated Private-Relay? This works as an Proxy service and makes it impossible for snapdrop to show the devices to each other. When you deactivate it via settings>iCloud>Private Relay everything should work as intended. If that's your matter this is a duplicate of #355 . See also this comment.
Thank you, but Private Relay is off.
-- Todd Benivegna // @.*** @.***
On 11/14/2022 2:12 PM EST schlagmichdoch @.***> wrote:
Do you have iCloud+ and activated Private-Relay? This works as an Proxy service and makes it impossible for snapdrop to show the devices to each other. When you deactivate it via settings>iCloud>Private Relay everything should work as intended. If that's your matter this is a duplicate of #355 https://github.com/RobinLinus/snapdrop/issues/355 . See also this comment https://github.com/RobinLinus/snapdrop/issues/355#issuecomment-932887098.
— Reply to this email directly, view it on GitHub https://github.com/RobinLinus/snapdrop/issues/536#issuecomment-1314248948, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKON5O3XZS7ESFRHV6MDUCDWIKFI5ANCNFSM6AAAAAAR6NCCYU. You are receiving this because you authored the thread.Message ID: @.***>
Also, am running it in Docker. Have the port opened in docker and in the server OS firewall.
Is this only an issues with your local version or is it failing on snapdrop.net
as well?
Snapdrop works by grouping all devices with the same public IP adress together. If you see different IP adresses when visiting e.g. https://www.whatismyip.com/ with your Mac vs your iPhone the network settings on your Mac or iPhone somehow change the IP adress by routing their connection through a proxy or VPN.
When the problem only occurs in your local version you would need to provide more information:
- Do you have problems reaching the page itself or are your devices simply not showing?
- Where is the Docker hosted? On one of the Macs or on a third device? Do you talk to your docker locally only or is your service publicly available?
- Do all devices have the same public IP adress?
Please provide your docker logs
- snapdrop.net works no problem.
- My iPhone has the same public IP as my WAN, so there is no proxy or VPN.
- I am able to load the local site on my iPhone as well as any other device.
- The snapdrop Docker container is on a separate device (Ubuntu server 20.04)
- The Docker container is only available locally
- All devices have the same public IP address
- Log: https://gist.github.com/influx3k/110de53248088daa7798c770c2e3d7dd
I followed these instructions to install: https://github.com/RobinLinus/snapdrop/blob/master/docs/local-dev.md
Should I install using instructions from LinuxServer? See below: https://hub.docker.com/r/linuxserver/snapdrop
Thanks.
It should work with just the docker-compose file found in this repository. When I tried to reproduce your problem I became aware that the p2p channels are often not correctly opened especially with Firefox. Tried to fix this with a PR waiting to be merged: #537 .
Maybe try it again with the source branch: https://github.com/schlagmichdoch/snapdrop/tree/show_peer_on_channel_open Also try to use private tabs or clear your safari website data for your domain.
Snapdrop works by grouping all devices with the same public IP adress together.
Leaving this note for others - this line helped me solve my issue.
MacBook Air M2 - MacOS 13.0 - Chrome 107.0.5304.110 iPhone 13 Pro - iOS 16.1.1 - Safari 3.6
I first launched the site on both devices and they couldn't see each other. Then I remember my VPN client was connected on the MacBook and I disconnected it.
I tried to refresh on both sides but I couldn't get them to work until I shift+refresh on the macbook.
Disable iCloud Private Relay https://filedrop.codext.de/
Was already mentioned and it was off/disabled. Still had same issue.
Today I setup my own instance, couldn't get it to work locally based on IP + port, but when I add it to an external domain and valid SSL, it instantly worked. So for me it was the issue that it needed to be a secure socket.