0

Youtube connection not working...

I guess when it rains it pours. I have 3 accounts on youtube for streaming. When using the interface in Wirecast to setup to a youtube stream I get this... see images. It worked yesterday morning but not in the afternoon. The RTMP works just fine. Using the latest version of Wirecast on a Mac.

69replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Greg Kuhnert So they definitely made the change recently which was either adding the # sent to us or changing so that they reject the # coming back to them (that they added). Yes so it's possible we can strip it going back but that they made a change, caused the issue.

    Like
  • Greg Kuhnert Thanks for putting us on the path though. Based on your comment we were able to figure exactly where this was happening.

    Like
  • Greg Kuhnert 🍺💯

    Like
  • CraigS said:
    So they definitely made the change recently which was either adding the # sent to us or changing so that they reject the # coming back to them (that they added). Yes so it's possible we can strip it going back but that they made a change, caused the issue.

    I had a look, and saw their response as you indicated. I agree 100% it was a youtube change that caused it. It would be nice if there was an API recording of past behaviour... that way, it would be trivial to show Google "You did this, and you broke it". Please back-out your change.

    I'll have a quick read of the oauth2 RFC's - out of interest, to see if the modification of scope that google is doing should be carried onto the token request or not... It would be nice to politely direct google to "Please obey the RFC's"

    Like
  • CraigS I had a look at RFC6749... It is not explicitly described, but I will give you my interpretation just for a laugh.

       The authorization server MAY fully or partially ignore the scope
       requested by the client, based on the authorization server policy or
       the resource owner's instructions.  If the issued access token scope
       is different from the one requested by the client, the authorization
       server MUST include the "scope" response parameter to inform the
       client of the actual scope granted.

    So. Google is only meant to return a scope response to the authorisation request If the issued access token scope is different from the one requested by the client

    Now if we assume the authorisation scope from Google is DIFFERENT, we should assume this is the scope that we will request a scope against. It does not explicitly say that, but I think your coders were correct in that interpretation.

    So. Google. "Please explain why your authorisation request has a scope that is different to the requested scope? And, if it is different - why you subsequently deny a token request for the scope that you authorised?"

    Now that I've read this, I think your code is 100% valid - and google's changes were 100% stupid... But its up to you if you want to push them to fix their shit, or be pragmatic and workaround their poor implementation.

    GK

    Like
  • Greg Kuhnert We will talk to them (with paddle in hand?) but at least we know what to do on our end if met with the immovable object.

    Like
  • CraigS - For information sake, I had a think about what they've probably done. I think Google is thinking about sub-scopes, with the idea that an individual user might be only allowed to access some components of the YouTube platform. That user might get a scope that has #chat for example on the end for the subscope. And they've probably updated their authorisation system to append the subscope ... but if that subscope is null, it should not be appending the #

    So - for your implementation of a workaround - you should keep your code as it is - and ONLY strip the # if it is at the end of the scope string that you get back from youtube. That will ensure any subsequent changes they make wont break anything else :)

    GK

    Like
  • gakgoka it's back to work yesterday  work great:D

    Like
  • gakgoka Good to hear.

    Like
  • May be totally irrelevant, but my desperation workaround was to reuse a saved .wcst document (Wirecast Pro 9.0.1) from a show I did a few months ago.  I opened it in Wirecast Pro 10.1 and it authenticated with no issue.

    Like
  • Warren Evans It's possible there was a saved "oauth token." It should be working again though. Issue was something they fixed.

    Like
  • CraigS I just tested it with success.  Thanks!

    Like
  • Warren Evans You're welcome of course. Thanks for the confirmation.

    Like
  • Working again for some reason...!

    Like
  • David Brewer YouTube fixed it.

    Like
  • Hi,

    I'm setting up my Wirecast gear 230 with version 12.1.0 and I'm running into the "Not Configured" from YouTube. Any thoughts or updates I should know about?

    Thanks

    Like
  • Keith Urban I'd like to help but I need more specific details about how you're setting up the event in Wirecast or whether you're doing that in YouTube's "Control Room." 

    Like
  • I know this is a year old but I'm having this problem as well
     

    Like
  • Matt St. Onge Wirecast 13.0.2? Try creating a scheduled event first. Quit and restart Wirecast. See if you can stream to YouTube.

    Like
  • CraigS I'm also having the same trouble. It was working and now it isn't. I'm using 13.0.2. I have quit and restarted to no avail. I have sent in a support ticket.

    I have a scheduled event...doesn't seem to be able to see it. It can't authenticate.

    Like
  • Daniel, log into YT and copy the stream settings from there. Use custom RTMP in Wirecast with the data and you should be good to go.

    Keep in mind that you have to start and stop in YT doing so. Not Wirecast like if you login through wirecast.

    Like
  • Daniel Kay said:
    have a scheduled event...doesn't seem to be able to see it.

     Authentication is the issue or not seeing the event?
    Please explain because you wouldn't get to Events until Authentication happens.

    Like
  • CraigS Jens Jarke I have resolved my issue...somehow! Don't really know what I did in all of my fiddlings! Thanks for your attention to my call for help.

    Like
  • Daniel Kay I think there are some YouTube "hiccups" in the move to their new Creator Studio. It seems to clear up though as you describe.

    Like
  • So is this not fixed then?  I'm really annoyed by spending so much money on something that literally works 30% of the time. I can't even get it to open on my new macbook and have to use my old computer, which luckily I didn't sell.  Connecting to Youtube should be the most basic thing. It literally worked last week, now it doesn't. Same with the software on my newer MBP.  Works fine, everything is set up, I reset the computer, now it won't connect. Amazing! 

    Like 1
Like Follow
  • 1 mth agoLast active
  • 69Replies
  • 1897Views
  • 19 Following