Site serving blank page after setting up forwarding from GoDaddy to Heroku (frame error?)

Question

I have a domain through GoDaddy, and set it up to forward to my app on heroku (I was using forwarding with masking). This was working great, until I tried to add an A-record to enable forwarding from a naked URL. Now, when I go to my site, I get a blank page, and the error message:

Refused to display 'myherokuurl' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.

And the source code in dev tools is a frame src. I have no idea why. I deleted the extra A-record that seems to have caused this problem almost 48 hours ago (so I don't think DNS propagation is an issue anymore). This is how I currently have everything set up in the DNS zone in GoDaddy:

My A records:

My CNAME:

And I have forwarding with masking set up to go to my heroku URL.

I also notice that when I run host www.mysiteurl.com, I get www.mysiteurl.com is an alias for mysiteurl.com.

Isn't that supposed to be www.mysiteurl.com is an alias for http://myherokuapp.herokuapp.com?

I'm using Cedar 14 stack on Heroku, and have read that A-records don't play nicely with that, so I'm tempted to delete my A-record and just go with what I have in the CNAME, but I'm afraid I'll further screw things up.

I really don't know what to do and am at the end of my rope with this. If anyone could offer any piece of advice or guidance, I'd really appreciate it.

have you check this http://stackoverflow.com/questions/20498831/refused-to-display-in-a-frame-because-it-set-x-frame-options-to-sameorigin — Arvind, Mar 01 '17 at 03:56
Yes, I've seen that-- that person didn't seem to be having any DNS set up issues. — tx291, Mar 01 '17 at 04:00
I have 2 cname records, 1 with www and other one for the base domain. It works fine with heroku. Though I am using bigrock, not godaddy. — Sajan, Mar 01 '17 at 05:22

score 0 · Answer 1 · answered Mar 01 '17 at 15:45

So it looks like the key issue to solving this was to remove the "forwarding with masking" option from GoDaddy--that's what broke everything, despite their telling me that the DNS was just updating and I needed to wait 48 hours -_-

My only issue now is just that the heroku url appears in my browser when I land on my site!

score 0 · Answer 2 · answered Feb 15 '18 at 08:57

You just have to enable IFrame support, by adding this to your application.rb file:

class Application < Rails::Application
  # ...
  # ...
  # insert here the following code:

  config.action_dispatch.default_headers = {
  'X-Frame-Options' => 'ALLOWALL'
  }
end

Then push to Heroku, the error message and blank page should disappear to show your page normally.

Site serving blank page after setting up forwarding from GoDaddy to Heroku (frame error?)

2 Answers2