search

mgozdiskowski / youtube-direct

Automatically exported from code.google.com/p/youtube-direct
0 stars 0 forks source link

Authentication Problem #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
When I try to authenticate the Youtube Account (Configuration / Youtube API 
Settings) I get the 
following message:

The page you have requested cannot be displayed. Another site was requesting 
access to your 
Google Account, but sent a malformed request. Please contact the site that you 
were trying to use 
when you received this message to inform them of the error.

Thanks.

Original issue reported on code.google.com by hdann...@gmail.com on 23 Nov 2009 at 9:06

GoogleCodeExporter commented 8 years ago 
I have sama problem....

Original comment by tv5polev...@gmail.com on 16 Dec 2009 at 2:52

GoogleCodeExporter commented 8 years ago 
Is that the error you received while running YTD on localhost? I received a 
whole
slew of errors running locally. So I deployed to app engine and it started
authenticating ok.

Original comment by jamesmeh...@gmail.com on 6 Jan 2010 at 7:35

GoogleCodeExporter commented 8 years ago 
Please make sure that you follow the directions in the "Registering your 
website for 
AuthSub" section of http://code.google.com/p/youtube-direct/wiki/GettingStarted

Specifically, if you enter a value for the "Target URL path prefix:" setting 
that doesn't 
match what you actually use to access your YouTube Direct App Engine instance, 
you'll get that malicious web site warning message.

Be sure to use http://APP_ID.appspot.com/ (where APP_ID is the name of your App 
Engine instance). It should be http:// and not https://

Original comment by api.je...@gmail.com on 7 Jan 2010 at 8:48

GoogleCodeExporter commented 8 years ago 
Yes, I follow all the directions from the documentation. According to people 
from
YouTube we contacted this is the normal behavior and people must click the 
"trust"
button. We didn't insist about this issue but by your answer it seems that is 
not the
normal behavior after all.

Original comment by hdann...@gmail.com on 7 Jan 2010 at 8:59

GoogleCodeExporter commented 8 years ago 
I'm also still having problems with this. 
I've followed instuctions step by step, checked out all the suggestions for 
fixes and
implemented them, but it still won't authenticate.
Help. I need to deploy this thing tomorrow morning.

I'd start everything from scratch with a new GAE account and youtube account, 
but
google only allows one verification code via sms per cellphone.
Kind of silly.

Original comment by rabblede...@gmail.com on 11 Jan 2010 at 8:18

GoogleCodeExporter commented 8 years ago 
Anyone?
Deadlines loom, and I've really tried everything.

Original comment by rabblede...@gmail.com on 11 Jan 2010 at 9:04

GoogleCodeExporter commented 8 years ago 
fixed. 
re-syncing with current SVN trunk solved the problem. Other users had suggested 
using
a previous version instead when they ran into this bug.

Original comment by rabblede...@gmail.com on 12 Jan 2010 at 10:05