-
Notifications
You must be signed in to change notification settings - Fork 41
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
HTTPS clients can't discover each other, but can discover and be discovered by HTTP-only clients #30
Comments
After communicating with the libp2p team a bit more, I'm unsure where in the IPFS/libp2p stack this is occurring. The following is a simplified version of the code I'm using to test
I've ruled out browser-specific issues by testing each affected machine with the IPFS benchmark tool which connects me (and every other browser I've tested) to other peers as expected. |
I think you need to remove Math.Random() when deploying. And one of my implementation is working on https on firebase. |
@harrshasri can you link to that implementation? |
This demo code doesn't seem to work once pushed behind an HTTPS endpoint. Specifically, HTTPS clients are communicating with the signaling server, but they're never made aware of one another. HTTP-only clients don't have this issue, and the interesting part is that an HTTP-only client can also discover and be discovered by HTTPS clients. There's just the disconnect between HTTPS clients and other HTTPS clients.
I thought maybe it was the signaling server, so I deployed my own libp2p-websocket-star rendezvous server to no avail. Am I missing something?
The text was updated successfully, but these errors were encountered: