# Supporting iframe embeds from different domains?
**URL:** https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930
**Category:** Feature
**Created:** [09.Июль.2015 15:30:50 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930 "2015-07-09T15:30:50Z")
**Posts on this page:** 19
**Page:** 3
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [27.Май.2017 18:01:07 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/43 "2017-05-27T18:01:07Z")
> [@tophee](#):
>
> I am not a RegEx expert and was not able to figure out how to specify a list of allowed TLDs.
Simply replacing `[a-z]{2,3}` with something like `(com|de|org)` should work 🙂
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [27.Май.2017 19:00:05 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/44 "2017-05-27T19:00:05Z")
Well except for many other TLDs like `.community` and the like..
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [27.Май.2017 19:04:07 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/45 "2017-05-27T19:04:07Z")
Sorry, I don’t understand. As far as I understood, @tophee was looking for a way to restrict the fuzzy match above to a concrete list of TLDs. google.community doesn’t appear to resolve to anything, but if @tophee wants to whitelist it anyways, adding it to the list like `(com|de|org|community)` should work, right?
---
### Author:  [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [27.Май.2017 19:08:33 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/46 "2017-05-27T19:08:33Z")
Yes. BTW, does anyone know where to find a complete list of all TLDs used by a service such as YouTube or Google Books?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [27.Май.2017 19:14:08 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/47 "2017-05-27T19:14:08Z")
Sure just reminding people that .com isn’t the only TLD any more.. there are zillions of them and I’m not just talking about .co.uk either!
---
### Author:  [@stabares](https://meta.discourse.org/u/stabares)
#### Post date: [28.Май.2017 17:56:37 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/48 "2017-05-28T17:56:37Z")
Hi! I’m using this plugin to embed a go board on my forum, but the iframe size is too small.
Is there any way to change its size?
You can see a test on:
[http://mrbaduk.com/t/test-gokibitz-iframe/75](http://mrbaduk.com/t/test-gokibitz-iframe/75)
The embed link is:
` `
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [28.Май.2017 19:41:38 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/49 "2017-05-28T19:41:38Z")
> [@stabares](#):
>
> Is there any way to change its size?
Yes. You can’t use a `style` attribute - it gets stripped out by Discourse. Also, the `script` tag will be stripped out. You don’t need it for displaying the iframe.
The height has to be set to a fixed number. I think the only attributes you can use are `width`, `height`, and `frameborder.` Try something like:
```plaintext
```
---
### Author:  [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [29.Май.2017 19:36:26 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/50 "2017-05-29T19:36:26Z")
> [@tophee](#):
>
> BTW, does anyone know where to find a complete list of all TLDs used by a service such as YouTube or Google Books?
To answer my own question, here seems to be a good place to look:
[https://en.wikipedia.org/wiki/List\_of\_Google\_domains](https://en.wikipedia.org/wiki/List_of_Google_domains)
Considering the length of that list, I almost think the simple fuzzy match option might actually be better that including the whole list in your regex. The most pragmatic approach is probably to pick a few TLDs based on where your membership sits and add more based on complaints. It’s really only an issue for highly international communities anyway.
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [15.Июль.2017 19:49:45 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/51 "2017-07-15T19:49:45Z")
If you’re using a fork of the Iframe Whitelist plugin with Discourse 1.9.0, you’ll need to sync your fork with the latest version, found here: [https://github.com/scossar/whitelist-iframe](https://github.com/scossar/whitelist-iframe).
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [04.Сентябрь.2017 20:12:16 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/52 "2017-09-04T20:12:16Z")
For anyone using the whitelist-iframe plugin, it is broken on the latest version of Discourse (1.9.0.beta8.) There is now an allowed iframes setting on the Discourse settings page. Remove the whitelist-iframe plugin and add any iframe sources you would like to whitelist to that setting.
---
### Author:  [@Cozdabuch](https://meta.discourse.org/u/Cozdabuch)
#### Post date: [14.Сентябрь.2017 09:49:17 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/53 "2017-09-14T09:49:17Z")
anyone know the whitelist address (to put in settings) for any of these sites?
kind of a noob here
> **[timeanddate.com](https://www.timeanddate.com)**
>
> Welcome to the world's top site for time, time zones, and astronomy. Organize your life with free online info and tools you can rely on. No sign-up needed.
> **[Make Your Countdown Timer For Free - TickCounter](https://www.tickcounter.com)**
>
> Free online countdown timer to share with friends or embed in your website as a widget. Beautiful, easy-to-use and highly customizable - make yours now!
> **[Create a Countdown Clock](https://countingdownto.com)**
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [14.Сентябрь.2017 21:58:09 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/54 "2017-09-14T21:58:09Z")
Hmm is this countdown scenario a use case for your Chrono plugin @j.jaffeux?
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [14.Сентябрь.2017 22:12:50 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/55 "2017-09-14T22:12:50Z")
[countingdownto.com](http://countingdownto.com) gives an iframe that you can use for embedding. On the latest version of Discourse you can whitelist it with the ‘allowed iframes’ site setting. ~~You have to supply the full URL, including all the digits for each timer you wish to embed (`https://w2.countingdownto.com/1944356`)~~
Edit: all you need to enter in the setting is the domain (`https://w2.countingdownto.com`)
---
### Author:  [@tokenl](https://meta.discourse.org/u/tokenl)
#### Post date: [13.Ноябрь.2017 02:54:58 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/56 "2017-11-13T02:54:58Z")
Hi, i installed the plugin, and rebuild done. but there is a error when posts alert `500 Internal Server Error`, like this
```plaintext
whilteListIframe is not a function
```
this is my discourse version.
is this version can’t user this plugins ?
**can you help me ? Thanks!**
this is error log:
```plaintext
Message (5 copies reported)
Job exception: TypeError: (0 , _sanitizer.whiteListIframe) is not a function
Backtrace
JavaScript at :4:34
JavaScript at mod.state (:164:29)
JavaScript at tryFinally (:30:14)
JavaScript at require (:162:5)
JavaScript at :262:22
JavaScript at Array.forEach ()
JavaScript at setup (:260:36)
JavaScript at buildOptions (:108:36)
JavaScript at :19:17
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/mini_racer-0.1.11/lib/mini_racer.rb:176:in `eval_unsafe'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/mini_racer-0.1.11/lib/mini_racer.rb:176:in `block (2 levels) in eval'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/mini_racer-0.1.11/lib/mini_racer.rb:256:in `timeout'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/mini_racer-0.1.11/lib/mini_racer.rb:175:in `block in eval'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/mini_racer-0.1.11/lib/mini_racer.rb:68:in `block in with_lock'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/mini_racer-0.1.11/lib/mini_racer.rb:68:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/mini_racer-0.1.11/lib/mini_racer.rb:68:in `with_lock'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/mini_racer-0.1.11/lib/mini_racer.rb:173:in `eval'
/var/www/discourse/lib/pretty_text.rb:190:in `block in markdown'
/var/www/discourse/lib/pretty_text.rb:391:in `block in protect'
/var/www/discourse/lib/pretty_text.rb:390:in `synchronize'
/var/www/discourse/lib/pretty_text.rb:390:in `protect'
/var/www/discourse/lib/pretty_text.rb:136:in `markdown'
/var/www/discourse/lib/pretty_text.rb:237:in `cook'
/var/www/discourse/app/models/post_analyzer.rb:24:in `cook'
/var/www/discourse/app/models/post.rb:249:in `cook'
/var/www/discourse/app/models/post.rb:484:in `rebake!'
/var/www/discourse/plugins/discourse-narrative-bot/jobs/onceoff/remap_old_bot_images.rb:30:in `block in execute_onceoff'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:63:in `block (2 levels) in find_each'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:63:in `each'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:63:in `block in find_each'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:129:in `block in find_in_batches'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:230:in `block in in_batches'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:214:in `loop'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:214:in `in_batches'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:128:in `find_in_batches'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:62:in `find_each'
/var/www/discourse/plugins/discourse-narrative-bot/jobs/onceoff/remap_old_bot_images.rb:20:in `execute_onceoff'
/var/www/discourse/app/jobs/onceoff.rb:21:in `execute'
/var/www/discourse/app/jobs/base.rb:134:in `block (2 levels) in perform'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rails_multisite-1.1.1/lib/rails_multisite/connection_management.rb:73:in `with_connection'
/var/www/discourse/app/jobs/base.rb:129:in `block in perform'
/var/www/discourse/app/jobs/base.rb:125:in `each'
/var/www/discourse/app/jobs/base.rb:125:in `perform'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:188:in `execute_job'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:170:in `block (2 levels) in process'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/middleware/chain.rb:128:in `block in invoke'
/var/www/discourse/lib/sidekiq/pausable.rb:80:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/middleware/chain.rb:130:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/middleware/chain.rb:133:in `invoke'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:169:in `block in process'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:141:in `block (6 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/job_retry.rb:97:in `local'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:140:in `block (5 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq.rb:36:in `block in '
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:136:in `block (4 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:204:in `stats'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:131:in `block (3 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/job_logger.rb:7:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:130:in `block (2 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/job_retry.rb:72:in `global'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:129:in `block in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/logging.rb:44:in `with_context'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/logging.rb:38:in `with_job_hash_context'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:128:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:168:in `process'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:85:in `process_one'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/processor.rb:73:in `run'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/util.rb:16:in `watchdog'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/sidekiq-5.0.5/lib/sidekiq/util.rb:25:in `block in safe_thread'
```
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [13.Ноябрь.2017 03:51:38 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/57 "2017-11-13T03:51:38Z")
The plugin will not work on your version of Discourse. You will need to remove it from your `app.yml` file and run `./launcher rebuild app`.
You can now whitelist iframe URLs through the Discourse admin/security page.
> [@simon](#):
>
> For anyone using the whitelist-iframe plugin, it is broken on the latest version of Discourse (1.9.0.beta8.) There is now an allowed iframes setting on the Discourse settings page. Remove the whitelist-iframe plugin and add any iframe sources you would like to whitelist to that setting.
---
### Author:  [@tokenl](https://meta.discourse.org/u/tokenl)
#### Post date: [13.Ноябрь.2017 05:54:18 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/58 "2017-11-13T05:54:18Z")
thank you very mach. it work nice.
---
### Author:  [@xiasummer](https://meta.discourse.org/u/xiasummer)
#### Post date: [30.Август.2018 18:32:41 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/60 "2018-08-30T18:32:41Z")
This question is very important, and also it’s tooooo long……Could you please select one post as the best solution?
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [30.Август.2018 18:58:52 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/61 "2018-08-30T18:58:52Z")
iframes can now be whitelisted through the **allowed iframes** Site Setting.
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [30.Август.2018 18:58:56 UTC](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930/62 "2018-08-30T18:58:56Z")
[Previous page](https://meta.discourse.org/t/supporting-iframe-embeds-from-different-domains/30930.md?page=2)