Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem configuring imbedded Elasticsearch (Bitbucket)

Joe Roper August 20, 2019

I am trying to configure the imbedded instance of Elasticsearch in my new Bitbucket install.  I have added the following lines to the bitbucket.properties file:

plugin.search.elasticsearch.baseurl=http://ibc-qctappd01:7992/

plugin.search.elasticsearch.username=username

plugin.search.elasticsearch.password=password

but when I restart the Bitbucket and Elasticsearch services (Windows Server 2016), and press the TEST button in the Admin screen, I am greeted by the following response:

"Access to Elasticsearch was denied. Check your settings."

Please help.  :-)

1 answer

0 votes
Charity Britton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 21, 2019

This can be due to numerous issues. Can you verify that any old process that was running on port 7992 is stopped. If you do see an old process running make sure Bitbucket services are COMPLETELY STOPPED before killing off the process. 

Joe Roper August 21, 2019

Checked using NETSTAT -B and Elasticsearch is the only process running on port 7992.

I made sure that the username and password matched in bitbucket.properties and buckler.yml before restarting both the Bitbucket and Elasticsearch services.

Still getting the message "Access to Elasticsearch was denied. Check your settings." when I click the TEST button in Bitbucket.

Charity Britton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 21, 2019

What version of Bitbucket are you running? Also we’re services stopped when you ran the netstat command?

Like Joe Roper likes this
Joe Roper August 22, 2019

Version 6.4.0.  Yes, the services were shutdown when I issued the NETSTAT -B command.  I guess I should clarify my previous statement...when the services were up, ElasticSearch was the only thing on port 7992, when I shutdown the services, nothing was running on 7992.  When I try to use a browser to get to ElasticSearch, I am greeted by a username/password window that doesn't like the username and password that I configured in bitbucket.properties and bucklet.yml.

Joe Roper August 27, 2019

Any further assistance would be greatly appreciated.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events