# Reporting behind secured apache proxy

**URL:** <https://discuss.elastic.co/t/reporting-behind-secured-apache-proxy/71251>\
**Category:** Kibana\
**Tags:** elastic-stack-reporting\
**Created:** [January 11, 2017, 4:14pm UTC](https://discuss.elastic.co/t/reporting-behind-secured-apache-proxy/71251 "2017-01-11T16:14:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Borrelworst](https://avatars.discourse-cdn.com/v4/letter/b/6f9a4e/32.png) [@Borrelworst](https://discuss.elastic.co/u/Borrelworst)\
**Post date:** [January 11, 2017, 4:14pm UTC](https://discuss.elastic.co/t/reporting-behind-secured-apache-proxy/71251/1 "2017-01-11T16:14:22Z")

</div>

Hi all,

I try to configure the reporting function while using Kibana behind a secured apache proxy: This does not seem to work. I almost tried everything I can think of, I will explain my configuration:

Apache is redirecting traffic coming in at port 1000, to kibana who listens on port 5602, with documentroot /kibana. This all works fine. However when using this configuration for the reporting it does not work:

xpack.reporting.enabled: true  
xpack.reporting.kibanaApp: "/kibana/app/kibana" \<\< normally it will be /app/kibana but I use as root /kibana so it becomes /kibana/app/kibana/  
xpack.reporting.kibanaServer.port: 1000  
xpack.reporting.kibanaServer.hostname: "serverName"  
xpack.reporting.kibanaServer.protocol: "http"  
xpack.reporting.queue.timeout: 300000

1. There are not settings for entering username/password
2. If I do not use all of these settings, it does not work as well.

Maybe someone has experienced the same issue, please let me know!

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [January 11, 2017, 5:20pm UTC](https://discuss.elastic.co/t/reporting-behind-secured-apache-proxy/71251/2 "2017-01-11T17:20:24Z")

</div>

In what way isn't reporting working after you added those additional settings?

Are you currently using the x-pack security plugin as well? If you do so, you shouldn't be having to hardcode the username/password anywhere.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 8, 2017, 5:20pm UTC](https://discuss.elastic.co/t/reporting-behind-secured-apache-proxy/71251/3 "2017-02-08T17:20:29Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.