This is still happening. Have you heard anything form Stream support?
This is still happening. Have you heard anything form Stream support?
Syep,
They are currently investigating and addressing the issue. If you have any additional details or error descriptions, feel free to leave a comment.
https://community.cloudflare.com/t/experiencing-intermittent-segment-errors-canceled-video-streaming/808125/20
They are currently investigating and addressing the issue. If you have any additional details or error descriptions, feel free to leave a comment.
https://community.cloudflare.com/t/experiencing-intermittent-segment-errors-canceled-video-streaming/808125/20
PHi everyone, simple question here, how can I have the data of viewers count if I choose to not show it embeded in the player ? Is there anywhere in the dashboard where I could find theses stats (currently only found minutes delivered in the analysis) ? The current comportement seems to be that if I de activate the viewers counter in the player, I can no longer access it trought the API even if i'm authenticated.
MCloudflare Docs
The Stream player has full support for live viewer counts by default. To get the viewer count for live videos for use with third party players, make a GET request to the /views endpoint.
THeya! Trying to stream into Cloudflare Stream using WebRTC - the SDP exchange is succesful, STUN is also succesful, but dTLS handshake times out. It looks like the Cloudflare server is ignoring our ClientHello message. Is there any way to find out why?
TMy own software (MistServer). I'm compatibility testing our new WHIP implementation against Cloudflare, trying to figure out why it's not working.
I know my network config and the connection should succeed like this - other tools can also connect just fine despite sending almost identical UDP packets. (There are some small differences in the dTLS ClientHello because our dTLS stack is using mbedtls as the library while most other tools out there use other libs - but I don't see any differences that should change the outcome.... and I tried setting the ciphersuite configuration identical to e.g. Chrome's defaults and that made no difference either
)
I should have mentioned the STUN messages that are succeeding are the ones to cloudflare's WebRTC IP/port returned from the SDP, not a separate STUN server. Which is to say, there is already bidirectional traffic on that UDP localport/localip/remoteport/remoteip combination, so I would expect that the ClientHello is actually arriving, but Cloudflare's server is purposefully not responding to it... for reasons I can't really debug.
I know my network config and the connection should succeed like this - other tools can also connect just fine despite sending almost identical UDP packets. (There are some small differences in the dTLS ClientHello because our dTLS stack is using mbedtls as the library while most other tools out there use other libs - but I don't see any differences that should change the outcome.... and I tried setting the ciphersuite configuration identical to e.g. Chrome's defaults and that made no difference either
)I should have mentioned the STUN messages that are succeeding are the ones to cloudflare's WebRTC IP/port returned from the SDP, not a separate STUN server. Which is to say, there is already bidirectional traffic on that UDP localport/localip/remoteport/remoteip combination, so I would expect that the ClientHello is actually arriving, but Cloudflare's server is purposefully not responding to it... for reasons I can't really debug.
T(And, of course, the same code does work with several other endpoints we've tried pushing to - so it must be some incompatibility that is in the implementation details...)
AHello, I was wondering how to activate Stream WebRTC (WHIP/WHEP) live inputs? Trying to do live streaming on a web app I am building, read that it is in beta and needs to get enabled?
SHi- I've got a couple questions.
First- what's the status of WebRTC for Cloudflare Stream? Doesn't seem to be much progress over the past year and am wondering if we need to be looking for another WebRTC solution (recording, analytics, simulcast etc).
Second- When we create a live input, and use a browser to stream using whip- we often get poor audio quality (compressed/distorted). This has happened on multiple PCs, as well as Macs, using multiple browsers, as well as multiple sound conversion devices. We can use an app like Vmeter to change audio drivers, which will eventually resolve the issue, however there doesn't seem to be a pattern to or consistency to resolving it. Anyone else experienced this?
First- what's the status of WebRTC for Cloudflare Stream? Doesn't seem to be much progress over the past year and am wondering if we need to be looking for another WebRTC solution (recording, analytics, simulcast etc).
Second- When we create a live input, and use a browser to stream using whip- we often get poor audio quality (compressed/distorted). This has happened on multiple PCs, as well as Macs, using multiple browsers, as well as multiple sound conversion devices. We can use an app like Vmeter to change audio drivers, which will eventually resolve the issue, however there doesn't seem to be a pattern to or consistency to resolving it. Anyone else experienced this?
1RealtimeKit is what you will be looking for regarding a good WebRTC solution
SThank you-
HWill cloudflare support in a near future rtmp on stream?
HSome manufacturers like black magic supports rtmp but not rtmps
T... is this channel ever read by anyone that actually works at cloudflare? I get the distinct impression that there simply is no actually useful support. (If there is a better place to get answers I'd love to know about it, but everywhere seems to direct to this Discord server...)
(If there is a better place to get answers I'd love to know about it, but everywhere seems to direct to this Discord server...)
1What issues are you having with Stream?
TNo response to the WHIP dTLS ClientHello. The message I posted a few days ago mentioned it (15 messages up from this one, and the couple messages right below).
I think the only way to further debug this is to get some information from the receiving side to understand why the handshake is being ignored, but I'm not aware of any way to get that information.
I think the only way to further debug this is to get some information from the receiving side to understand why the handshake is being ignored, but I'm not aware of any way to get that information.
TYeah, I tried everything I could think of and at this point am stuck. But we're not going to pay for anything remotely close to enterprise because 1) support experience so far is absolutely terrible and 2) we're not even the client. We're building this integration for others, not for ourselves. We don't even use any cloudflare service whatsoever - our customers do.
So I guess we'll just recommend competing services to our customers in the meanwhile.
So I guess we'll just recommend competing services to our customers in the meanwhile.
TWe are a competitor to those, so that doesn't make sense.
KIs it possible to add CORS headers in the response received from cloudflare stream similar to R2?
MNot sure if anyone can help -- I uploaded about 45k video clips to Stream yesterday. I have validated in the API that all are reporting
state: ready and pctComplete: 100.0000 in their statuses. YET, the majority will not stream or embed yet, even though the thumbnails are present. Is there a silent backend processing I am not aware of that I need to wait for before the videos are all actually streamable?
Mfor the record, for allowed origins ["*"] does not equal []
TSure. If anyone could tell me how cloudflare's WebRTC infra worked..? Can't a/b anything if it's a black box. But I'm going to make some assumptions on what cloudflare probably is using under the hood (I found an open source WebRTC library that exhibits the same behaviour, at least...) and work on resolving that and hope that it fixes cloudflare too.
NHello, I have an issue for one video on mu Stream account (I have the 50$ per month plan), its ok for 100+ videos, but only one stay in "Pending Upload" statut since more than 48 hrs, it's my biggest file, 2.8 Go, maybe for that reason ? :x Thanks for help!
1The size shouldn't matter, I regularly upload 5GB+ files. Are you uploading the file yourself? I would retry the upload
NI already tried 2 times, at different days, so weird
1Are you uploading via the UI in Stream or via API/tus?
Nvia the UI, drag n drop
1So are you confirming that the upload actually completes?
1Like there's a progress bar you need to wait for
Nmm i didnt remember see the full 100% bar in front of me, I'll try again and watch carefully is the load is full
1yeah you always wanna wait for the bar to finish lol if you navigate away it cancels the upload and the existing upload will sit in that pending state forever
MHi guys,
I'm trying to use Cloudflare Stream's Signed URLs feature to protect a video, but I'm consistently getting a 401 Unauthorized error when hls.js attempts to load the HLS manifest.
My Cloudflare Worker successfully generates the JWT token (all blue logs), and the exp claim is in the future. The accessRules in the token's payload are set to [{ type: "any", action: "allow" }]. I have also correctly configured "Allowed origins" for the video in the Stream dashboard to my Webflow domain.
Despite this, Stream returns 401 Unauthorized when the player tries to fetch the manifest.
Could you please help me understand why the token is being rejected? Could you check your internal logs for this video UID and the provided token to identify the exact reason for the 401?
Thank you!
I'm trying to use Cloudflare Stream's Signed URLs feature to protect a video, but I'm consistently getting a 401 Unauthorized error when hls.js attempts to load the HLS manifest.
My Cloudflare Worker successfully generates the JWT token (all blue logs), and the exp claim is in the future. The accessRules in the token's payload are set to [{ type: "any", action: "allow" }]. I have also correctly configured "Allowed origins" for the video in the Stream dashboard to my Webflow domain.
Despite this, Stream returns 401 Unauthorized when the player tries to fetch the manifest.
Could you please help me understand why the token is being rejected? Could you check your internal logs for this video UID and the provided token to identify the exact reason for the 401?
Thank you!
1Honestly I doubt you'll be able to get someone to look at your logs. I'd try without the Alowed Origin set, and also check that your token expiry is far in the future
VHi there! Do you use Cloudflare @Images or @Stream ? If so, we’d love to hear about your experiences and any pain points you may have encountered. We’re conducting a brief survey to better understand your needs and to help us improve our media platforms. Your feedback is incredibly valuable and will play a key role in shaping future updates. Interested? Please click this link to take the survey. Thank you for your time!
SAlthough this channel isn't specifically for Cloudflare Images, I thought I'd share my query here too, as Stream is a related product
R?crossposting general-helpCloudflare Images Browser Cache TTL
SPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
SApologies
1What do you mean by store in the cloud after they're done? Stream offers both of those features
1Not super relevant to that survey, I just want someone from the media team/s that is semi active here on Discord. Whether its for simple troubleshooting, or keeping us in the loop regarding developments
