We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to replace Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed directly, but we need authentication and whatever I do I cannot make it work from behind reverse proxy! Early or later I get 401 accessing some internal resource.
Wonder if anybody hit similar problem and have any insight how to make it work.
We cannot use Shield as its price is way beyond our bounds.
Disable Output cache for the website you are using as reverse proxy.
Run the website in a new apppool, which do not have any managed code.
With the above two steps, kibana4 runs fine with IIS as reverse proxy.
On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman wrote:
We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for
auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to replace
Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed
directly, but we need authentication and whatever I do I cannot make it
work from behind reverse proxy! Early or later I get 401 accessing some
internal resource.
Wonder if anybody hit similar problem and have any insight how to make it
work.
We cannot use Shield as its price is way beyond our bounds.
Thank you for the good news! I'm a little swamped currently, but I will
definitely give it a try when I get a minute.
Just to make sure - "disable Output cache for the website" - where is it in
IIS Management Console?
On Wednesday, January 28, 2015 at 4:38:01 PM UTC-8, Cijo Thomas wrote:
Its possible to use IIS with the following steps.
Disable Output cache for the website you are using as reverse proxy.
Run the website in a new apppool, which do not have any managed code.
With the above two steps, kibana4 runs fine with IIS as reverse proxy.
On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman wrote:
We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for
auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to replace
Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed
directly, but we need authentication and whatever I do I cannot make it
work from behind reverse proxy! Early or later I get 401 accessing some
internal resource.
Wonder if anybody hit similar problem and have any insight how to make it
work.
We cannot use Shield as its price is way beyond our bounds.
I have been fighting with this for quite some time, Finally found the
workaround. Let me know if it helps you!
On Thu, Jan 29, 2015 at 10:12 AM, Konstantin Erman konste@gmail.com wrote:
Thank you for the good news! I'm a little swamped currently, but I will
definitely give it a try when I get a minute.
Just to make sure - "disable Output cache for the website" - where is it
in IIS Management Console?
On Wednesday, January 28, 2015 at 4:38:01 PM UTC-8, Cijo Thomas wrote:
Its possible to use IIS with the following steps.
Disable Output cache for the website you are using as reverse proxy.
Run the website in a new apppool, which do not have any managed code.
With the above two steps, kibana4 runs fine with IIS as reverse proxy.
On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman
wrote:
We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for
auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to replace
Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed
directly, but we need authentication and whatever I do I cannot make it
work from behind reverse proxy! Early or later I get 401 accessing some
internal resource.
Wonder if anybody hit similar problem and have any insight how to make
it work.
We cannot use Shield as its price is way beyond our bounds.
On Thursday, January 29, 2015 at 10:13:40 AM UTC-8, Cijo Thomas wrote:
I have been fighting with this for quite some time, Finally found the
workaround. Let me know if it helps you!
On Thu, Jan 29, 2015 at 10:12 AM, Konstantin Erman <kon...@gmail.com
<javascript:>> wrote:
Thank you for the good news! I'm a little swamped currently, but I will
definitely give it a try when I get a minute.
Just to make sure - "disable Output cache for the website" - where is it
in IIS Management Console?
On Wednesday, January 28, 2015 at 4:38:01 PM UTC-8, Cijo Thomas wrote:
Its possible to use IIS with the following steps.
Disable Output cache for the website you are using as reverse proxy.
Run the website in a new apppool, which do not have any managed code.
With the above two steps, kibana4 runs fine with IIS as reverse proxy.
On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman
wrote:
We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for
auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to replace
Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed
directly, but we need authentication and whatever I do I cannot make it
work from behind reverse proxy! Early or later I get 401 accessing some
internal resource.
Wonder if anybody hit similar problem and have any insight how to make
it work.
We cannot use Shield as its price is way beyond our bounds.
On Thursday, January 29, 2015 at 10:13:40 AM UTC-8, Cijo Thomas wrote:
I have been fighting with this for quite some time, Finally found the
workaround. Let me know if it helps you!
On Thu, Jan 29, 2015 at 10:12 AM, Konstantin Erman kon...@gmail.com
wrote:
Thank you for the good news! I'm a little swamped currently, but I will
definitely give it a try when I get a minute.
Just to make sure - "disable Output cache for the website" - where is it
in IIS Management Console?
On Wednesday, January 28, 2015 at 4:38:01 PM UTC-8, Cijo Thomas wrote:
Its possible to use IIS with the following steps.
Disable Output cache for the website you are using as reverse proxy.
Run the website in a new apppool, which do not have any managed code.
With the above two steps, kibana4 runs fine with IIS as reverse proxy.
On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman
wrote:
We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for
auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to replace
Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed
directly, but we need authentication and whatever I do I cannot make it
work from behind reverse proxy! Early or later I get 401 accessing some
internal resource.
Wonder if anybody hit similar problem and have any insight how to make
it work.
We cannot use Shield as its price is way beyond our bounds.
On Thursday, January 29, 2015 at 10:13:40 AM UTC-8, Cijo Thomas wrote:
I have been fighting with this for quite some time, Finally found the
workaround. Let me know if it helps you!
On Thu, Jan 29, 2015 at 10:12 AM, Konstantin Erman kon...@gmail.com
wrote:
Thank you for the good news! I'm a little swamped currently, but I will
definitely give it a try when I get a minute.
Just to make sure - "disable Output cache for the website" - where is
it in IIS Management Console?
On Wednesday, January 28, 2015 at 4:38:01 PM UTC-8, Cijo Thomas wrote:
Its possible to use IIS with the following steps.
Disable Output cache for the website you are using as reverse proxy.
Run the website in a new apppool, which do not have any managed
code.
With the above two steps, kibana4 runs fine with IIS as reverse proxy.
On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman
wrote:
We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for
auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to replace
Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed
directly, but we need authentication and whatever I do I cannot make it
work from behind reverse proxy! Early or later I get 401 accessing some
internal resource.
Wonder if anybody hit similar problem and have any insight how to
make it work.
We cannot use Shield as its price is way beyond our bounds.
I hit the same issue when accessing the site using DNS name. When I am in
the machine, http:localhost:xxxx/ works though. Have not figured out the
fix for this yet. It seems like Kibana 4 CORS issue.
On Thu, Jan 29, 2015 at 3:38 PM, Konstantin Erman konste@gmail.com wrote:
Yes, Kibana 4 beta 3. And I have just one URL rewrite rule (pictured).
Were you getting the same error when it was not working for you?
On Thursday, January 29, 2015 at 10:13:40 AM UTC-8, Cijo Thomas wrote:
I have been fighting with this for quite some time, Finally found the
workaround. Let me know if it helps you!
On Thu, Jan 29, 2015 at 10:12 AM, Konstantin Erman kon...@gmail.com
wrote:
Thank you for the good news! I'm a little swamped currently, but I
will definitely give it a try when I get a minute.
Just to make sure - "disable Output cache for the website" - where is
it in IIS Management Console?
On Wednesday, January 28, 2015 at 4:38:01 PM UTC-8, Cijo Thomas wrote:
Its possible to use IIS with the following steps.
Disable Output cache for the website you are using as reverse
proxy.
Run the website in a new apppool, which do not have any managed
code.
With the above two steps, kibana4 runs fine with IIS as reverse proxy.
On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman
wrote:
We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for
auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to replace
Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed
directly, but we need authentication and whatever I do I cannot make it
work from behind reverse proxy! Early or later I get 401 accessing some
internal resource.
Wonder if anybody hit similar problem and have any insight how to
make it work.
We cannot use Shield as its price is way beyond our bounds.
Well, access through localhost worked for me from the very beginning, as
well as access through LAN. But external access is also necessary, that's
where the whole issue with IIS reverse proxy stemmed from!
On Friday, February 6, 2015 at 4:30:47 PM UTC-8, Cijo Thomas wrote:
I hit the same issue when accessing the site using DNS name. When I am in
the machine, http:localhost:xxxx/ works though. Have not figured out the
fix for this yet. It seems like Kibana 4 CORS issue.
On Thu, Jan 29, 2015 at 3:38 PM, Konstantin Erman <kon...@gmail.com
<javascript:>> wrote:
Yes, Kibana 4 beta 3. And I have just one URL rewrite rule (pictured).
Were you getting the same error when it was not working for you?
On Thursday, January 29, 2015 at 10:13:40 AM UTC-8, Cijo Thomas wrote:
I have been fighting with this for quite some time, Finally found the
workaround. Let me know if it helps you!
On Thu, Jan 29, 2015 at 10:12 AM, Konstantin Erman kon...@gmail.com
wrote:
Thank you for the good news! I'm a little swamped currently, but I
will definitely give it a try when I get a minute.
Just to make sure - "disable Output cache for the website" - where is
it in IIS Management Console?
On Wednesday, January 28, 2015 at 4:38:01 PM UTC-8, Cijo Thomas wrote:
Its possible to use IIS with the following steps.
Disable Output cache for the website you are using as reverse
proxy.
Run the website in a new apppool, which do not have any managed
code.
With the above two steps, kibana4 runs fine with IIS as reverse
proxy.
On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman
wrote:
We currently use Kibana 3 hosted in IIS behind IIS reverse proxy
for auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to
replace Kibana 3 soon. Kibana 4 is self hosted and works nicely when
accessed directly, but we need authentication and whatever I do I cannot
make it work from behind reverse proxy! Early or later I get 401 accessing
some internal resource.
Wonder if anybody hit similar problem and have any insight how to
make it work.
We cannot use Shield as its price is way beyond our bounds.
I just found the solution for this problem in my case.
The problem is occurring because ISS server is classifying the request "/elasticsearch/.kibana/_mapping/*/field/source?=1453386587718" as a "potentially dangerous Request".
So, after i realized that i just change my web.config file to ignore this validation, as seen bellow:
I am confused now! When I logged to my IIS servers to apply your fix, Marcus, to my surprise I have found that those two lines are already there! Now I have no idea how they got there in the first place, but I don't remember adding those manually. Could some other process add those for me? Puzzling...
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.