This repository has been archived by the owner on Apr 25, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 196
gst-rust can't connect to WebSocket #120
Comments
Can you check with wireshark what it actually tries to do there and attach the capture as pcap/pcapng file? Only the communication with |
I attached two captures below. It seems there are some connection reset thing going on, but I'm really not familiar with this area so I'll leave it to you to take a look. Thanks! |
🤦♂️ Yes. See websockets-rs/rust-websocket#237 |
nirbheek
added a commit
that referenced
this issue
Jul 15, 2019
Empty string or `None` mean all interfaces. Specifying 0.0.0.0 means ipv4 interfaces only. Fixes #120
The server now listens on ipv4 and ipv6. I've pushed a commit that makes this the default: da27e59 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm on macOS 10.14.5 and have installed all the GStreamer plugins via Homebrew. I cloned this repo, went into the
sendrecv/gst-rust
directory and compiled it successfully withcargo build
. However, when I tried to docargo run -- --peer-id=x
wherex
is the ID I got from https://webrtc.nirbheek.in/, the program failed with the following output:The Python example works fine though, so I doubt it's a Firewall issue. Could you provide some insights on what might be the cause here? Let me know if you need more debug info.
The text was updated successfully, but these errors were encountered: