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

400 Client Error: Bad Request #310

Closed
iPickedScout opened this issue Sep 14, 2016 · 8 comments
Closed

400 Client Error: Bad Request #310

iPickedScout opened this issue Sep 14, 2016 · 8 comments

Comments

@iPickedScout
Copy link

Whenever I attempt to open I stream, it keeps sending the message:
"Unable to open URL: https://api.twitch.tv/api/channels//access_token.json (400 Client Error: Bad Request)"
It was happening before the 0.14.2 update as well, so it isn't caused by that. I didn't see any other issues for this, so I don't know if it is just on my end.

@bastimeyer
Copy link
Member

This is a Livestreamer related issue: chrippa/livestreamer#1456

Twitch is finally making the planned changes live that all API requests need to have a client-id included by the requesting application. See https://api.twitch.tv/api/channels/access_token.json in your browser. I upgraded the GUI a couple of weeks ago, so that it includes the ID even while not being logged in.

I'm not getting this error yet, but you can read here that they are testing it, so maybe not globally accross their network. Livestreamer doesn't include the client-id, so that's why you're seeing this error.

I don't know though if this issue will be resolved soon. Livestreamer is not being actively maintained anymore, but there are people who are trying to organize a fork. #289

@bastimeyer
Copy link
Member

The issue can be fixed by using a Twitch OAuth token, which means that you have to be logged in to your Twitch account in the GUI as long as there is no Livestreamer upgrade.

This also means that I need to require an active login-session in the GUI for being able to launch streams and also add an error message for this. I might upload a new release because of this...

Funny coincidence for feature request #308...

bastimeyer added a commit that referenced this issue Sep 14, 2016
bastimeyer added a commit that referenced this issue Sep 14, 2016
and implement ModalAuthRequiredComponent.
See #310
@jspraul
Copy link

jspraul commented Sep 15, 2016

Client-ID might be enough right now?

chrippa/livestreamer#1478 (comment)

@bastimeyer
Copy link
Member

Yes, this seems to be the better solution, thanks!
I didn't notice that the --http-header parameter was available, because I just quickly looked at the code of Livestreamer's twitch plugin...

The auth restriction can be removed again. I'm going to release v0.15.1 once I have fixed the Windows tray icon regression #312.

@BrandonDenton
Copy link

I have registered my app with my Twitch account and received a client ID. Where exactly in a Python "requests" library request would I include this client ID? Would it be another argument to requests.get()?

@bastimeyer
Copy link
Member

@BrandonDenton
Wrong repo...

@bastimeyer
Copy link
Member

I think this can be closed now after a year of Livestreamer being broken in its default configuration. I don't expect many people to run into this issue anymore.

To the people still using Livestreamer: please switch to Streamlink.
Thanks...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants