Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selfhosted not working: Docker on Pi 4, Portainer. Not visible to other devices in the network #354

Open
jnanadarshan opened this issue Sep 25, 2021 · 10 comments

Comments

@jnanadarshan
Copy link

I installed using Linuxserver.io image from docker hub via Portainer GUI. Used only given parameters like config, PUID, PGID and TZ. The issue is when I open my Pi 4 IP HTTP://xx.xx.xx.xx:8851 or https://xx.xx.xx.xx:8853 on the same device with the same or different browsers I see the devices. If I open on any other device I'm not able to see other devices. (Mac, Windows, Android, iOS tried everything).

The website snapdrop.net works fine on all devices so I'm guessing no changes necessary on Network Config or device config.

Do I need to change something on Conf files to make this work on self-hosted instances? Am I missing some things?

@peterlang-p
Copy link

peterlang-p commented Oct 1, 2021

Same issue for me. I also tried using the "original" version of this repo link but seems not to work either.

@bennyzen
Copy link

bennyzen commented Oct 3, 2021

Same here. Deployed locally, no errors, but devices cannot see each other.

@geminos-dev
Copy link

Installed via supplied Docker-compose.yaml and also cannot see any other devices. Also see a connection timeout banner every 5 seconds

@kliarist
Copy link

Same here. I have just tried and it wont discover devices on the same network.

@peterlang-p
Copy link

I don't know how or if this helps, but I got it working for me by routing snapdrop through traefik.
After accessing it via my url with ssl, both devices were found instantly.

In before I was trying to access my snapdrop instance via the ip:port

@r4tze
Copy link

r4tze commented Nov 26, 2021

I think it's because of the different IPs, when you connect from your internal network.
Snapdrop puts clients with the same source ip (usually the WAN IP of your router) in one "Share-Room"
Check this Issue out #159 and try to apply the "sed" commands to your container. then it should work.

@schlagmichdoch
Copy link
Contributor

This would be fixed if #558 was merged.

@aboodvan
Copy link

aboodvan commented Feb 3, 2023

Same here. I tried sed command but i get this error:

sed: server/index.js: No such file or directory

@schlagmichdoch
Copy link
Contributor

@aboodvan Have you tried the pull request #558 as well?

@aboodvan
Copy link

aboodvan commented Feb 3, 2023

Thank you @schlagmichdoch
sed -i 's/peer.ip/0/g' server/index.js fixed it for me

I'm new to linux and I just learned that "ls -R index.js" wouldn't search inside directories.

I used "find -name index.js" and I fount out that www/ should be included as the file was in that directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants