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

Not working on mobile using PeerjsTransporter #11

Open
tur-ing opened this issue Jan 15, 2021 · 4 comments
Open

Not working on mobile using PeerjsTransporter #11

tur-ing opened this issue Jan 15, 2021 · 4 comments

Comments

@tur-ing
Copy link

tur-ing commented Jan 15, 2021

The project works locally on PC using LocalStorageTransporter and also Peerjs as server:

Local peerjs settings:

1:1 in same browser works
1:1 in Chrome <> Safari works

But it doesn’t work hosted on EC2 using PeerjsTransport on mobile devices:

Remote peerjs settings:

  • peerHost: 18.197.123.66
  • peerPort: 9000
  • peerPath: /myapp

1:1 does not work in same browser
1:1 does not work in same browser on different devices

@tur-ing tur-ing changed the title Works locally using Peerjs but not on EC2 Works locally using Peerjs but not on remote environment Jan 16, 2021
@tur-ing
Copy link
Author

tur-ing commented Jan 17, 2021

Does anybody have an idea what the issue might be? Thanks

@tur-ing tur-ing changed the title Works locally using Peerjs but not on remote environment Works not on mobile using PeerjsTransporter Jan 18, 2021
@tur-ing tur-ing changed the title Works not on mobile using PeerjsTransporter Not working on mobile using PeerjsTransporter Jan 18, 2021
@nlokhande1
Copy link

nlokhande1 commented Jun 27, 2022

@tur-ing Hello, is it working with a remote peer server? why did you strikeout that title? It is only working on localhost for us and not on remote , thanks

@nlokhande1
Copy link

@Yuyz0112 any updates/pointers regarding this issue? thanks

@Juice10
Copy link
Contributor

Juice10 commented Mar 13, 2023

Hi @tur-ing and @nlokhande1, thanks for submitting this issue. The syncit project got moved to the rrweb-io GitHub org, and this repo will get archived soon. Would you mind re-submitting your issue there if it is still relevant for the new 1.0.1 (rrweb 2.0 based) syncit?

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

3 participants