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

[Bug]: Webgear_RTC Requires security downgrade #341

Closed
3 tasks done
KhanMechAI opened this issue Nov 21, 2022 · 3 comments
Closed
3 tasks done

[Bug]: Webgear_RTC Requires security downgrade #341

KhanMechAI opened this issue Nov 21, 2022 · 3 comments
Assignees
Labels
EXTERNAL BUG 👾 Bug caused by external dependent library INVALID 🛑 This doesn't seem right or non-applicable or missing information

Comments

@KhanMechAI
Copy link

Description

I have a simple Webgear_RTC with a custom source (which shouldnt be relevant, but in case it is).
Using Brave Browser, but have also tested safari and Chrome with the same issue.
I can start the server, open the streaming page no worries. The ICE connection handshake begins, but fails.
The work-around is to disable your security settings and the handshake will succeed, and streaming will start.

Not sure if this is a bug or proposal, but I guess as its not documented that this si the expected behaviour then I would consider it a bug.

This issue only started in the last week or two, it was working beforehand - cant pinpoint exact date though sorry.

Issue Checklist

  • I have searched open or closed issues for my problem and found nothing related or helpful.
  • I have read the Documentation and found nothing related to my problem.
  • I've read the Issue Guidelines and wholeheartedly agree.

Expected behaviour

Webgear_RTC stream to work successfully with default browser security settings.

Actual behaviour

Webgear_RTC only works by disabling Browser security.

Steps to reproduce

  1. Setup a Webgear_RTC stream
  2. Open a modern browser with default security settings
  3. You should see the regular page you have for your server, with the black streaming box in the center. It will never load.
  4. The server will show a failed ICE handshake

Terminal log output

No response

Python Code

No response

VidGear Version

0.2.6

Python version

3.10.8

OpenCV version

4.6

Operating System version

debian bullseye

Any other Relevant Information?

No response

@KhanMechAI KhanMechAI added the BUG 🐛 Vidgear api's error, flaw or fault label Nov 21, 2022
@welcome
Copy link

welcome bot commented Nov 21, 2022

Thanks for opening this issue, a maintainer will get back to you shortly!

In the meantime:

  • Read our Issue Guidelines, and update your issue accordingly. Please note that your issue will be fixed much faster if you spend about half an hour preparing it, including the exact reproduction steps and a demo.
  • Go comprehensively through our dedicated FAQ & Troubleshooting section.
  • For any quick questions and typos, please refrain from opening an issue, as you can reach us on Gitter community channel.

@abhiTronix
Copy link
Owner

The work-around is to disable your security settings and the handshake will succeed, and streaming will start.

I think this issue is related to aiortc library which is used as WebGear_RTC API's backend. Can you cross-check by playing with given demo examples?

@abhiTronix abhiTronix added WAITING TO TEST ⏲️ Asked user to test the suggested example/binary/solution WAITING FOR RESPONSE ⏳ Waiting for the user response. labels Nov 23, 2022
@abhiTronix
Copy link
Owner

@KhanMechAI I think this is related: aiortc/aiortc#801

Anyways, this problem is related to aiortc library and not vidgear. Please raise this issue there

@abhiTronix abhiTronix added EXTERNAL BUG 👾 Bug caused by external dependent library INVALID 🛑 This doesn't seem right or non-applicable or missing information and removed WAITING TO TEST ⏲️ Asked user to test the suggested example/binary/solution WAITING FOR RESPONSE ⏳ Waiting for the user response. BUG 🐛 Vidgear api's error, flaw or fault labels Jan 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EXTERNAL BUG 👾 Bug caused by external dependent library INVALID 🛑 This doesn't seem right or non-applicable or missing information
Projects
None yet
Development

No branches or pull requests

2 participants