# Marvel Sense is not working over https **URL:** \ **Category:** Elasticsearch\ **Created:** [December 1, 2014, 5:14pm UTC](https://discuss.elastic.co/t/marvel-sense-is-not-working-over-https/21010 "2014-12-01T17:14:26Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Andrew\_Rimmer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_rimmer/32/1076_2.png) [@Andrew\_Rimmer](https://discuss.elastic.co/u/Andrew_Rimmer)\ **Post date:** [December 1, 2014, 5:14pm UTC](https://discuss.elastic.co/t/marvel-sense-is-not-working-over-https/21010/1 "2014-12-01T17:14:26Z")
Marvel Sense is not working, it hangs when it tried to connect to the Elasticsearch API.The rest of Marvel seems to be working fine, as does the Elasticsearch API if called directly. I am using a freshly installed Elasticsearch 1.4.1 and the latest Marvel. Elasticsearch is exposed on the internet over SSL as [https://mydomain/](https://mydomain/). When I profile the javascript in the browser, I can see that Marvel Sense actually tries to make the calls to the API over http, even though the API and Marval are using https. My Elasticsearch installation is not available over the internet to anything other than https. I have nginx installed, which passes the elasticsearch calls from 443 to 9200. Again this all works fine when calling the Elasticsearch API or the plugins etc. Any ideas? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c1672223-3a03-48a2-bf12-90f7938fa12c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c1672223-3a03-48a2-bf12-90f7938fa12c%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [December 3, 2014, 6:11am UTC](https://discuss.elastic.co/t/marvel-sense-is-not-working-over-https/21010/2 "2014-12-03T06:11:07Z")
Copy pasting from the relevant GitHub issue for future reference: ([https://github.com/elasticsearch/elasticsearch/issues/8735](https://github.com/elasticsearch/elasticsearch/issues/8735)) In the next marvel release we will have automatic support for this. I wonder if things would work for you if enter [https://mydomain/](https://mydomain/) in the server box of sense. It doesn't indeed listen to the config.js file of kibana. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/02107297-a29f-46b4-9532-51313551dbaf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/02107297-a29f-46b4-9532-51313551dbaf%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [December 20, 2014, 8:56am UTC](https://discuss.elastic.co/t/marvel-sense-is-not-working-over-https/21010/3 "2014-12-20T08:56:11Z")
A short note that the work around is not needed anymore with marvel 1.3.0. Cheers, Boaz On Wednesday, December 3, 2014 7:11:07 AM UTC+1, Boaz Leskes wrote: > Copy pasting from the relevant GitHub issue for future reference: ( > [Marvel Sense does not work over SSL · Issue #8735 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/8735)) > > In the next marvel release we will have automatic support for this. I > wonder if things would work for you if enter [https://mydomain/](https://mydomain/) in the > server box of sense. It doesn't indeed listen to the config.js file of > kibana. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/014eaa20-7125-414e-905c-38d0c5ef1b89%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/014eaa20-7125-414e-905c-38d0c5ef1b89%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:42am UTC](https://discuss.elastic.co/t/marvel-sense-is-not-working-over-https/21010/4 "2017-07-06T00:42:35Z")