mertushka
mertushka
@UnyeSpor This issue should remain open, as `haxball.js` still defaults to the `node-datachannel` library. As one of the contributors to `node-datachannel`, I believe addressing this would be beneficial for the...
@imDarvaged I can’t diagnose the issue just by looking at the error messages. I need a minimal script that reproduces the errors so I can understand what’s happening in the...
This should be fixed in `[email protected]`. The `node-datachannel` dependency has been updated to `v0.28.0` which addresses the underlying issue with data channel race conditions.
Add `debug: true` in your RoomConfig so we can see whats wrong with WebSocket connection.
I'm currently unsure why the proxy with credentials isn't working for you. I'll keep this issue open to see if anyone has a solution or further insights.
@jakjus In fact, I did try it when I first see this issue, and it just works as usual, even though I used free proxies. As for the actions, it...
@damian18zb The proxy functionality has been using the same underlying module `https-proxy-agent` since `v2.1.3`. So it can’t stop working with `v3.0.0`.
Closing this issue for now as it does not appear to be caused by a regression in `haxball.js`. The proxy feature relies on external factors like the proxy server configuration...
@murat-dogan Yes, it’s not related to data channels. The issue seems more like the peer connection is being destroyed before all ICE candidates are processed. I’m seeing `addRemoteCandidate()` throw when...
This should be fixed in `v3.0.1`.