# Site plugins not working for me on 0.17.9

**URL:** <https://discuss.elastic.co/t/site-plugins-not-working-for-me-on-0-17-9/5866>\
**Category:** Elasticsearch\
**Created:** [November 14, 2011, 3:26pm UTC](https://discuss.elastic.co/t/site-plugins-not-working-for-me-on-0-17-9/5866 "2011-11-14T15:26:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex\_At\_Ikanow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_at_ikanow/32/676_2.png) [@Alex\_At\_Ikanow](https://discuss.elastic.co/u/Alex_At_Ikanow)\
**Post date:** [November 14, 2011, 3:26pm UTC](https://discuss.elastic.co/t/site-plugins-not-working-for-me-on-0-17-9/5866/1 "2011-11-14T15:26:58Z")

</div>

I must be doing something stupid, but I can't work out what!  
Suggestions on what that might be or how to debug further much  
appreciated...

See the following gist: [https://gist.github.com/1364037](https://gist.github.com/1364037)

I install the plugin (happy), check I am running 0.17.9 (I'm upgrading  
my pseudo-production environment from 0.16.x) and then try to access  
the bigdesk site plugin (the behavior vs elasticsearch-head is  
identical)

Either via curl or firefox I get a blank response back from the  
server.

Any ideas?

(Looking at the source code, I can't see any useful logging statements  
I could turn on. Next step would be sticking some print statements in  
I guess, so I'm hoping someone else has had a similar problem and was  
more competent at fixing it!)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [November 15, 2011, 11:06am UTC](https://discuss.elastic.co/t/site-plugins-not-working-for-me-on-0-17-9/5866/2 "2011-11-15T11:06:31Z")

</div>

Strange..., just double checked fresh 0.17.9 install and it works (its very  
important to have the last /, but you have it in the URL). Not sure whats  
missing, can you try on your own dev box and see if it works?

On Mon, Nov 14, 2011 at 5:26 PM, Alex at Ikanow [apiggott@ikanow.com](mailto:apiggott@ikanow.com) wrote:

> I must be doing something stupid, but I can't work out what!  
> Suggestions on what that might be or how to debug further much  
> appreciated...
> 
> See the following gist: [https://gist.github.com/1364037](https://gist.github.com/1364037)
> 
> I install the plugin (happy), check I am running 0.17.9 (I'm upgrading  
> my pseudo-production environment from 0.16.x) and then try to access  
> the bigdesk site plugin (the behavior vs elasticsearch-head is  
> identical)
> 
> Either via curl or firefox I get a blank response back from the  
> server.
> 
> Any ideas?
> 
> (Looking at the source code, I can't see any useful logging statements  
> I could turn on. Next step would be sticking some print statements in  
> I guess, so I'm hoping someone else has had a similar problem and was  
> more competent at fixing it!)

---

<div class="post-metadata">

**Author:** ![Alex\_At\_Ikanow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_at_ikanow/32/676_2.png) [@Alex\_At\_Ikanow](https://discuss.elastic.co/u/Alex_At_Ikanow)\
**Post date:** [November 15, 2011, 1:50pm UTC](https://discuss.elastic.co/t/site-plugins-not-working-for-me-on-0-17-9/5866/3 "2011-11-15T13:50:23Z")

</div>

Thanks for the sanity check and suggestion ... for some reason my /etc/  
init.d/elasticsearch file was setting es.path.home parameter twice on  
the command line, the second time to "".

I install/upgrade using Tavisto's RPMs, which have some "noreplace"  
clauses, so probably you can break the upgrade with suitable changing  
of config files between versions!

---

<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:** [July 6, 2017, 3:48am UTC](https://discuss.elastic.co/t/site-plugins-not-working-for-me-on-0-17-9/5866/4 "2017-07-06T03:48:35Z")

</div>


