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

[WebRTC] WHEPS sourceFingerprint not working #2618

Closed
1 of 13 tasks
tbnguyen1407 opened this issue Nov 1, 2023 · 2 comments · Fixed by #2626
Closed
1 of 13 tasks

[WebRTC] WHEPS sourceFingerprint not working #2618

tbnguyen1407 opened this issue Nov 1, 2023 · 2 comments · Fixed by #2626
Labels
bug Something isn't working webrtc

Comments

@tbnguyen1407
Copy link

Which version are you using?

v0.2.1

Which operating system are you using?

  • Linux amd64 standard
  • Linux amd64 Docker
  • Linux arm64 standard
  • Linux arm64 Docker
  • Linux arm7 standard
  • Linux arm7 Docker
  • Linux arm6 standard
  • Linux arm6 Docker
  • Windows amd64 standard
  • Windows amd64 Docker (WSL backend)
  • macOS amd64 standard
  • macOS amd64 Docker
  • Other (please describe)

Describe the issue

sourceFingerprint is not used to validate the cert when ingesting with WHEPS, throwing error:

tls: failed to verify certificate: x509: certificate signed by unknown authority

Ingesting using other encrypted protocols, e.g RTSPS, is working as intended.

Describe how to replicate the issue

Replicate by ingesting WHEP output of mediamtx in another path.

~ mediamtx.yml ~
## rtsps
protocols: [tcp]
encryption: "optional"
serverKey: key.pem
serverCert: cert.pem

## webrtc
webrtcEncryption: yes
webrtcServerKey: key.pem
webrtcServerCert: cert.pem

paths:
  path1:
    source: "rtsp://x.x.x.x:554/"
  ## proxy path1 using rtsps - working
  path2:
    source: "rtsps://127.0.0.1:8322/path1"
    sourceFingerprint: "41A231120E5DFD75A333EED014B7A79F2E216BC53288FF102EB8FC5CD527E9E1"
  ## proxy path1 using webrtc - not working
  path3:
    source: "wheps://127.0.0.1:8889/path1/whep"
    sourceFingerprint: "41A231120E5DFD75A333EED014B7A79F2E216BC53288FF102EB8FC5CD527E9E1"

  1. start the server
  2. see logs for error

Did you attach the server logs?

no

Did you attach a network dump?

no

Copy link
Contributor

This issue is mentioned in release v1.3.0 🚀
Check out the entire changelog by clicking here

Copy link
Contributor

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.

@github-actions github-actions bot locked and limited conversation to collaborators May 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working webrtc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants