Accounts-facebook fails when the site uses SSL


My app has so far lived “unsecured” - meaning no redirection to https:// by default. This has worked fine in conjunction with the accounts-facebook package, which creates its own SSL enabled connection to Facebook when doing its OAuth magic.

My problems started when I tried acessing my site using https instead of http. The pop-up window halts quickly and by reading its console output I can see the following message

Uncaught SecurityError: Blocked a frame with origin "" from accessing a frame with origin "".  The frame requesting access has a protocol of "http", the frame being accessed has a protocol of "https". Protocols must match.

I thought this might have something to do with the site url in the app’s facebook settings, but changing the http to https in that setting got me nowhere. Still got the same message. How is this supposed to work? I am not hardcoding the http part of the path anywhere except the facebook settings, so this seems to be something the accounts-facebook package is doing.

This is my app settings on Facebook. Observe the non-SSL site url. I am not allowed to put images in my post as a new user, but if I could, they would be found on this page:


Curious to know whether you figured it out? I have the same problem, but in reverse (trying to access http when the site and settings are https), and in Chrome but not Safari:


Nope, sorry. The way this forum works does not seem too great for gathering top content. Seems like the posts disappear. Try StackOverflow and see how far that gets you, and report back.

My workaround was to force http … which was fine for this small demo app.


I finally found a good piece of info. It turns out you need to set the ROOT_URL environment variable for the callbacks to work. See these SO links for more:
Google OAuth
Why is ROOT_URL a required environment variable for bundle deployment?


Thanks, but wasn’t a fix for me – was already setting ROOT_URL. Switching to redirect instead of popup for now.


I checked out your site now and see that you set “ROOT_URL”:“”, so that seems legit … Not seeing that error you talked about in that SO thread though (failing on first attempt).

Hope you find out what was your problem, and do post back here or on that SO question.