# Making discourseEmbedURL match expected topic requirements **URL:** \ **Category:** Product Support\ **Created:** [August 15, 2016, 4:59pm UTC](https://meta.discourse.org/t/making-discourseembedurl-match-expected-topic-requirements/48660 "2016-08-15T16:59:57Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Jeff\_Doran](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@Jeff\_Doran](https://meta.discourse.org/u/Jeff_Doran)\ **Post date:** [August 16, 2016, 6:40pm UTC](https://meta.discourse.org/t/making-discourseembedurl-match-expected-topic-requirements/48660/6 "2016-08-16T18:40:43Z")
Okay I was wondering about that, but these are just domains used to access separate discourse forum that we are wanting to use. One is an alias and the other is owned by disourse. How does someone use an embedded discourse site on a protected page served from https? I don’t think providing an ssl cert for the alias domain alone would work. I did consider copying and hosting the embed.js file from our server, but it conflicts with our gulp jslint requirements and that quickly proved untenable. I also thought of trying to proxy it though our nginx config might be an option, but I’d much rather see the ability to load embed.js from any https supported site. Or more directly, can I get an https url for my discourse forum ( ‘[lexmachina.bydiscourse.com](http://lexmachina.bydiscourse.com)’) ? --- _[View the full topic](https://meta.discourse.org/t/making-discourseembedurl-match-expected-topic-requirements/48660)._