Aloha Communtiy, i am trying to put discourse in an iframe since i don’t have free wildcards at my dyndny hoster. I run my main apache server at port 80 and the docker containing discourse redirects to port 82. the page i am talking about is here: http://archy.no-ip.org/forum/ instead of the discourse page at http://archy.no-ip.org:81 it just shows the blank container. i first thought that it might be a problem with iframe to shown pages which don’t use port 80 or 443 but since another test shows that my plone-environment at port 81 (http://archy.no-ip.org/iframe-test-different-port/) is shown correctly that cannot be it. Any ideas what’s wrong? thanks and greetings

I’m able to load Discourse in an iframe … on Firefox. But not Chrome (or Safari). In Chrome I have the following problem: Nothing is clickable! If I open the inspector and drill into the source it will highlight various elements (e.g. rows), but neither right clicks nor left clicks on any content of iframe have an effect. Any suggestions?

[תמונה] dubeydeepak: ll help in fixing issue Xframe option with sameorigin . w That not change the X-Frame-Options header flag…

There is some checksum or something… because if I modify this file the app wont start…

A solution to run Discourse in an iframe is to create a plugin that contains the following code in plugin.rb: # Changes X-Frame-Options so the site can be embedded in an iframe. See: # https://github.com/BeXcellent/discourse-allowiframe/blob/master/plugin.rb # https://github.com/TheBunyip/discourse-allow-same-origin/blob/master/plugin.rb Rails.application.config.action_dispatch.default_headers.merge!({'X-Frame-Options' => 'ALLOWALL'})

Thanks Jack! I was forked and uploaded a plugin on github in case of someone need it… plugin.rb master # name: Set X-Frame-Options correctly # about: Set site headers # version: 1 # authors: Julian Rails.application.config.action_dispatch.default_headers.merge!({'X-Frame-Options' => 'ALLOWALL'}) Rails.application.config.action_dispatch.default_headers.merge!({'Access-Control-Allow-Origin' => '*'}) Rails.application.config.action_dispatch.default_headers.merge!({'Access-Control-Allow-Methods' => 'GET, POST, OPTIONS, DELETE'}) Rails.application.config.action_dispatch.default_headers.merge!({'Access-Control-Allow-Headers' => 'Content-Type, Authorization, X-Requested-With'})

We do say this is unsupported for a reason. https://media.giphy.com/media/xT1R9KJH2bXffKbjwc/giphy.mp4

@Julian_Somoza, the Discourse team promotes an opinionated way of using Discourse and will not support alternatives. Additionally, they always reminds people of that fact. That being said, I’m not from the Discourse team, so I can discuss your issue :slight_smile: I use Discourse in an iframe for my project and never got the “You were logged out” modal.

And you just overrided the X-Frame-Options header or you did something else? We use Zimbra and want to put the Discourse inside a Zimlet…

Discourse not shown in iframe

Product Support

Julian_Somoza (Julian Somoza) 21 באוגוסט,‏ 2018,‏ 5:32pm 15

There is a new challenge now, inside the iframe appear an “You were logged out.” modal… I’m researching for solve this…

נושא		תגובות	צפיות
Whitelist, allowed iframe Feature	11	7116	27 בספטמבר,‏ 2018
Running Discourse in an iframe Product Support	8	2354	29 בדצמבר,‏ 2016
Support embedding Discourse in an iframe Feature embedding	16	8709	13 ביוני,‏ 2025
Iframes Not Working Product Support	6	1672	3 במרץ,‏ 2022
Cannot get embedding to work Product Support	11	2896	31 באוגוסט,‏ 2021

Discourse not shown in iframe

נושאים קשורים