Problem redirecting after facebook login on heroku (works fine locally)

907 views
Skip to first unread message

Rick Boardman

unread,
Jul 1, 2012, 12:37:23 AM7/1/12
to django-so...@googlegroups.com
I'm wondering if anyone can help me debug the following:

I'm testing django-social-auth for facebook login. The problem is that the facebook auth redirect works on my localhost but not on a remote host (deployed via heroku). When I FB login via my remote website, I just get redirected back to my homepage, not to my redirect URL.

Here are the configs and server log outputs. Any help with debugging appreciated!

My django-social-auth URL settings are the same on both:
LOGIN_URL          = '/'
LOGIN_REDIRECT_URL = '/home/'
LOGIN_ERROR_URL    = '/error/'

LOCAL HOST (WORKS AOK)
- login via my local website login page http://rick.pagekite.me -> /facebook/login
- see my facebook app dialog for local dev, click "go app"
- I get redirected to http://rick.pagekite.me/home/#_=_  SUCCESS! (-:

Local Facebook app:
PagekiteTTYFU
- App domain: pagekite.me
- Note I'm using pagekite to tunnel facebook auth to my localhost

Server logs:
[30/Jun/2012 23:32:52] "GET / HTTP/1.1" 200 955
[30/Jun/2012 23:32:54] "GET /login/facebook/ HTTP/1.1" 302 0
No handlers could be found for logger "SocialAuth"
[30/Jun/2012 23:33:06] "GET /complete/facebook/?code=AQBrnUmJRclz2Dhr5C9S-bWMPZT-DDIsfBnFhCC0NZsE6URAoTb4F0MPRY73smWlt8l7ySJuph_-zURxcrjXUWGRuiw0Vwk6f_j_GnfB5-rVYkUo0yU8FQB0lHOOEIHdvjn5dwyusJXNg-ecIwmq2XZyohc2TZS7cLQXVIAnI7zPowza1V9eXPpryhn3XnS4iCE HTTP/1.1" 302 0
[30/Jun/2012 23:33:06] "GET /home/ HTTP/1.1" 200 956

====

REMOTE HOST (PROBLEM)
- login via my remote website login http://www.ttyfu.com -> /facebook/login
- see my remote testing facebook app dialog, click "go app"
- I get redirected back to my login page http://www.ttyfu.com/#_=_ PROBLEM )-:

Remote Facebook app
HerokuTTYFU
- App domain: ttyfu.com

Server logs:
2012-07-01T04:34:36+00:00 app[web.1]: [30/Jun/2012 23:34:36] "GET /login/facebook/ HTTP/1.1" 302 0
2012-07-01T04:34:36+00:00 heroku[router]: GET www.ttyfu.com/login/facebook/ dyno=web.1 queue=0 wait=0ms service=8ms status=302 bytes=0
2012-07-01T04:34:43+00:00 app[web.1]: [30/Jun/2012 23:34:43] "GET /complete/facebook/?code=AQCg0LKAD-MEUMeYbBNUFNWYeUu4QozYIAkv66H-FQ0_LazV5gqhdkfzO8Q4D1GAOstuFHpyYVS2VywbdKeUl2tGC9zZjSTEp9h8x-qHGvyglqnR973h9T2PZ7Z0uB1-5YjW2WX2ZQa5yj10Gnc7z9wAYb5IzvQQwjpudISASPnHJL8LXKJj_HpILM_-48eQmVY HTTP/1.1" 302 0
2012-07-01T04:34:43+00:00 app[web.1]: [30/Jun/2012 23:34:43] "GET / HTTP/1.1" 200 955

Matías Aguirre

unread,
Jul 1, 2012, 1:54:29 AM7/1/12
to django-social-auth
Is the account logged in after the process finished? Otherwise it would imply
an error in the process and a setting misconfiguration.

Are you using the same Facebook App keys in your local setup and heroku?

Regards,
Matías

Excerpts from Rick Boardman's message of 2012-07-01 01:37:23 -0300:
> I'm wondering if anyone can help me debug the following:
>
> I'm testing django-social-auth for facebook login. The problem is that the
> facebook auth redirect works on my localhost but not on a remote host
> (deployed via heroku). When I FB login via my remote website, I just get
> redirected back to my homepage, not to my redirect URL.
>
> Here are the configs and server log outputs. Any help with debugging
> appreciated!
>
> My django-social-auth URL settings are the same on both:
> *LOGIN_URL = '/'
> *
> *LOGIN_REDIRECT_URL = '/home/'*
> *LOGIN_ERROR_URL = '/error/'*
>
> *LOCAL HOST (WORKS AOK)*
> *- login via my local website login page http://rick.pagekite.me
> -> /facebook/login*
> *- see my facebook app dialog for local dev, click "go app"*
> *- I get redirected to http://rick.pagekite.me/home/#_=_ SUCCESS! (-:*
>
> Local Facebook app:
> *- PagekiteTTYFU*
> *- Site URL: http://rick.pagekite.me*
> *- App domain: pagekite.me*
> - Note I'm using pagekite to tunnel facebook auth to my localhost
>
> Server logs:
> *[30/Jun/2012 23:32:52] "GET / HTTP/1.1" 200 955*
> *[30/Jun/2012 23:32:54] "GET /login/facebook/ HTTP/1.1" 302 0*
> *No handlers could be found for logger "SocialAuth"*
> *[30/Jun/2012 23:33:06] "GET
> /complete/facebook/?code=AQBrnUmJRclz2Dhr5C9S-bWMPZT-DDIsfBnFhCC0NZsE6URAoTb4F0MPRY73smWlt8l7ySJuph_-zURxcrjXUWGRuiw0Vwk6f_j_GnfB5-rVYkUo0yU8FQB0lHOOEIHdvjn5dwyusJXNg-ecIwmq2XZyohc2TZS7cLQXVIAnI7zPowza1V9eXPpryhn3XnS4iCE
> HTTP/1.1" 302 0*
> *[30/Jun/2012 23:33:06] "GET /home/ HTTP/1.1" 200 956*
>
> ====
>
> *REMOTE HOST (PROBLEM)*
> *- login via my remote website login http://www.ttyfu.com -> /facebook/login
> *
> *- see my remote testing facebook app dialog, click "go app"*
> *- I get redirected back to my login page http://www.ttyfu.com/#_=_ PROBLEM
> )-:*
>
> Remote Facebook app
> *- HerokuTTYFU*
> *- Site URL: http://www.ttyfu.com*
> *- App domain: ttyfu.com*
>
> Server logs:
> *
> 2012-07-01T04:34:36+00:00 app[web.1]: [30/Jun/2012 23:34:36] "GET
> /login/facebook/ HTTP/1.1" 302 0
> 2012-07-01T04:34:36+00:00 heroku[router]: GET www.ttyfu.com/login/facebook/
> dyno=web.1 queue=0 wait=0ms service=8ms status=302 bytes=0
> 2012-07-01T04:34:43+00:00 app[web.1]: [30/Jun/2012 23:34:43] "GET
> /complete/facebook/?code=AQCg0LKAD-MEUMeYbBNUFNWYeUu4QozYIAkv66H-FQ0_LazV5gqhdkfzO8Q4D1GAOstuFHpyYVS2VywbdKeUl2tGC9zZjSTEp9h8x-qHGvyglqnR973h9T2PZ7Z0uB1-5YjW2WX2ZQa5yj10Gnc7z9wAYb5IzvQQwjpudISASPnHJL8LXKJj_HpILM_-48eQmVY
> HTTP/1.1" 302 0
> 2012-07-01T04:34:43+00:00 heroku[router]: GET
> www.ttyfu.com/complete/facebook/?code=AQCg0LKAD-MEUMeYbBNUFNWYeUu4QozYIAkv66H-FQ0_LazV5gqhdkfzO8Q4D1GAOstuFHpyYVS2VywbdKeUl2tGC9zZjSTEp9h8x-qHGvyglqnR973h9T2PZ7Z0uB1-5YjW2WX2ZQa5yj10Gnc7z9wAYb5IzvQQwjpudISASPnHJL8LXKJj_HpILM_-48eQmVY
> dyno=web.1 queue=0 wait=0ms service=771ms status=302 bytes=0
> 2012-07-01T04:34:43+00:00 app[web.1]: [30/Jun/2012 23:34:43] "GET /
> HTTP/1.1" 200 955
> *
--
Matías Aguirre (matias...@gmail.com)

Rick Boardman

unread,
Jul 1, 2012, 11:13:48 PM7/1/12
to django-so...@googlegroups.com
Hi Matias,

Thanks for the reply!

I worked out what was going on - I'd forgotten to syncdb my remote database. Unfortunately heroku wasn't reporting any errors!

Cheers,

Rick
Reply all
Reply to author
Forward
0 new messages