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

supabase works local but not between different internet connections #89

Open
TrusteroP2P opened this issue Sep 24, 2024 · 2 comments
Open

Comments

@TrusteroP2P
Copy link

Uncaught Error: Connection failed.
at Ki._onConnectionStateChange (trystero-supabase.min.js:1)
at RTCPeerConnection._pc.onconnectionstatechange (trystero-supabase.min.js:1)

This is the error it gets. Worked fine with two tabs connecting with appId and api key in config. But the second I try to connect with a different device such as a phone, it fails and both instances give this error.

I was able to connect the two devices using one of the "less reliable" methods although as its said they cut out for a while sometimes.

@TrusteroP2P
Copy link
Author

TrusteroP2P commented Sep 27, 2024

actually I'm seeing this with other libraries as well just got it with nostr too, this just happens no matter what connection I try remotely. Its not even a reconnect like your prior filed issues, it just fails out the gate.

@TrusteroP2P
Copy link
Author

TrusteroP2P commented Sep 29, 2024

Under further analysis, supplying config file didn't actually get used, instead had to edit the min javascript libraries and add it through a global variable. Seems it needed TURN but I still see that error anyways. Seems like most issues are related to webRTC and the almost deliberately difficultly ISPs put everyone through. Note: happened on an older version of open source chromium for windows 7 to replicate it.

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

1 participant