500 Internal Server Error and Access-Control-Allow-Origin about github HOT 11 CLOSED

I am! See here http://markx.herokuapp.com/ when trying to sign in to GitHub by clicking the GitHub icon.
Strange things is, I didn't get this error when running on localhost.
See yoavram/markx#20.

from github.

I found a solution: following issue #8 I emailed @captn3m0 and got this response:

The error you get is because you have not created a github application with the correct domain. The code works on localhost, because someone has already made an app with localhost as the domain. However, the same code won't run on heroku because the domain is not whitelisted on github. To get it to whitelist, you need to create an application. You can create one at github.com/settings/applications/new

from github.

Hmmm...that seems like a pain (since I am not hosting my app anywhere at this time for implementation and testing), but thanks for the solution--I'll look into it :)

from github.

For me it came down to going github.com/settings/applications/new , entering an app name and a URL where it lives, and that's it, didn't have to change any code, just went on with the basic authentication. If you change URLs all the time you can either change them at the github settings too, or pop up a permanent proxy and tunnel all your api requests through it. I guess...

from github.

@michael , I think this issue can be closed - would you agree @MuffinTheMan ?

from github.

I would think so. Do you happen to know if I can set up my application with them and keep it private? I'm working on an app that I can't make public at this time..

from github.

I don't think they publicize the URL you give them, if that is what you mean.

from github.

Ok, cool. I wasn't sure if they used that for anything besides granting authorization. Thanks.

from github.

The previous comment is just my opinion, I can't really say what they do with it - you should ask them (@github on twitter?)

from github.

Got it, thanks!

from github.

Hey guys, I'm helping Michael clear old issues here and sounds like this can be closed.

I've also recently added notes and links to the readme file, re auth & tokens, to help people avoid setup issues such as this.

from github.