Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

WebTransport session establishment failed. Too many pending WebTransport sessions (64) #64

Open
achingbrain opened this issue Apr 13, 2023 · 2 comments

Comments

@achingbrain
Copy link
Member

Sometimes I see thousands instances of this warning in Chrome:

WebTransport session establishment failed. Too many pending WebTransport sessions (64)

image

This module may need some sort of dial queue to ensure it doesn't open too many connections and trigger this error.

@SgtPooki
Copy link
Member

we need to make sure we leave some webtransport sessions for peers to connect to the helia node

@achingbrain
Copy link
Member Author

achingbrain commented Jun 29, 2023

WebTransport is only for outgoing connections, not incoming. Only WebRTC can be used to dial in to browser nodes.

We do need to limit the number of in-flight WebTransport connections though, to be under browser limits.

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

No branches or pull requests

2 participants