You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
We're using Bitbucket server version 7.21.10 and its search functionality seems to be broken.
Test button in server settings gives access denied error. We did the steps mentioned in this article - Test button in Search server for Bitbucket server results in the access denied for resetting the search server password, but running securityadmin.sh script gives some SSL error while connecting to OpenSearch. Error log give below:
bash +x securityadmin.sh --port 7992 -f ../securityconfig/internal_users.yml -t internalusers -icl -nhnv -cacert /apps/bitbucket/data/shared/search/config/root-ca.pem -cert /apps/bitbucket/data/shared/search/config/bitbucket.pem -key /apps/bitbucket/data/shared/search/config/bitbucket-key.pem
WARNING: nor OPENSEARCH_JAVA_HOME nor JAVA_HOME is set, will use /usr/bin/java
Security Admin v7
WARNING: Seems you want connect to the OpenSearch HTTP port.
securityadmin connects on the transport port which is normally 9300.
Will connect to localhost:7992 ... done
00:57:05.585 [opensearch[_client_][transport_worker][T#1]] ERROR org.opensearch.security.ssl.transport.SecuritySSLNettyTransport - Exception during establishing a SSL connection: io.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record
OpenSearch certificates are all available in this folder - $bitbucket_home/shared/search/config including root-ca.pem, bitucket.pem and bitbucket-key.pem
Welcome to the Atlassian Community!
Please use the HTTPS port: 7993, and check if your file "internal_users.yml" has "admin" in the backend_role section.
Best regards,
Luiz
Thanks !
That worked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.