Jeff Thomas Atlassian Team

System Information should be available under Administration >> Support Tools >> System Information. The direct link is at http://stash.company.com/plugins/servlet/stp/view/

Hi Ryan, Which version of Bitbucket Server are you using? Are you using something like the External Hooks add-on or are you adding the hooks manually to the repository? If you're on Bitbucket Server 4.6+ and are using an add-on, I believe you're running into the bug described in BSERV-8606 - MergeRequest veto will display…

Hi Prameesha, The documentation you linked to is actually for Bitbucket Cloud, hosted at bitbucket.org. For Bitbucket Server, the URL structure is similar, but slightly different. If the repository is part of a project, use the following structure:…

Hi @Marc-Antoine LECLERCQ, Since netstat shows that something is listening on port 7990 and the logs don't show any errors, can you verify that the firewall allows connections on port 7990? Also, what is the result of running "curl http://localhost:7990" when on the server?

For Bitbucket Server, the server.xml is read from $BITBUCKET_HOME/shared/server.xml first, not from the installation directory. If you make the same changes to the shared directory and restart Bitbucket Server, the avatar should be loaded over HTTPS. More details available…

Hi Matt, The participant filters can just be tacked on as query parameters. For example, if you wanted to find all the pull requests where the "admin" user was a reviewer and had not approved them yet, you could run: curl -X GET \…

Hi Pavel, Yes this is possible. In your Markdown create a link at the top: [link](#section) and in the body of your document, create the anchor: <a name="section"></a>

FishEye is a tool of indexing your source code repositories and provides charts and information about it. You can browse the full source in the web interface and do full text searching, just to name a few features. More information is available at https://www.atlassian.com/software/fisheye As you mention, Crucible provides…

There has to be something that we're missing. If you'd like, I'd be happy to look at it together. Just shoot me a message at jethomas at atlassian dot com and we can set up a time to chat.

Have you run through any of the troubleshooting steps available at Troubleshooting steps for Bitbucket Server Code Search? Just based on the error you're seeing, it would imply that either Elasticsearch is not running or there is a firewall blocking the connection. If you SSH into the server and run "curl…

Since you get the same connection refused message using localhost, but this worked before, what has changed? Can you confirm that Bitbucket Server is still running? address="192.168.10.10" controls which IP address we'll bind to, but by default, this is not needed.

By default Bitbucket Server binds to 7990 and does not care which address you use to connect on port 7990. You can configure 'address="192.168.10.10"' to bind to a specific IP address, if multiple are available. If a reverse proxy is being used, proxyPort="80" and proxyName="mycompany.com" could be set, but no of these…

The base URL setting is stored in the DB, but this should not be causing a connection refused message.

What is the result of running the following: curl -iL http://bitbucket.domain.tld:7990 Are there any firewalls in place that would be blocking the request? Since you can hit this from a remote machine using the computer name on port 7990, this seems less likely, but worth checking.

You shouldn't need to configure anything within Bitbucket Server for the http://bitbucket.<doman_name>.<tld>:7990 URL to work. The connection refused message suggests that the URL above is not pointed to the correct server. If you run dig or ping to bitbucket.<doman_name>.<tld>, do you get a response and is it pointed at…

git status just returns information about the local working tree, it does not communicate out to the remote repository. https://git-scm.com/docs/git-status

Hi Mitch, Starting with Bitbucket Server 5.0, there is no longer a control port that is used by the application.

For Bitbucket Server, configuring pull request merge strategies via the UI was introduced in version 4.9.

We should see an error in the atlassian-bitbucket.log file which indicates why it failed to start. Can you find that log in $BITBUCKET_HOME/log and see what the error is?

Hi Neal, What is the SSL error that you're seeing? It looks like the ssl.enabled property is missing. Can you try adding the following and see if it resolves the error? server.additional-connector.1.ssl.enabled=true If you were following a guide for this, can you let me know which one? I want to make sure that property is…

That's correct, Bitbucket Server is only able to display files stored in LFS if they're stored locally. There is an open feature request to add support for using LFS with Artifactory which is being tracked at https://jira.atlassian.com/browse/BSERV-9721 There is also a more general feature request about supporting the use…

Hi Majus, I'm not able to reproduce what you're seeing at the moment. When I delete a tag via the REST API and refresh the commits page in the UI, the tag no longer appears. Which version are you running? I did my testing on Bitbucket Server 4.14.4.

Hi Majus, Looking at the REST documentation you linked, it looks like the endpoint you should be hitting is /rest/git/1.0, not /rest/api/1.0: url = '{}/rest/git/1.0/projects/{}/repos/{}/tags/{}'.format(url, project_name, repo_name, tag) # where tag is '1.0' Can you try updating the URL and see if that resolves the issue?…

Hi Bruce, You should be able to use Includes to limit which paths that will be indexed. Checkout the documentation at Include Exclude paths and let me know if you have any questions. Cheers, Jeff

Hi, Deleting the repository from FishEye/Crucible will not delete the repository from the remote SVN server. FishEye/Crucible are read-only for the remote repository, so you can safely delete the repository and the remote SVN repository will remain untouched. Cheers, Jeff

Hi Sean, The repository-config file won't exist until you're running at least 4.12. Since you're on 4.8, the DB query should give you the information you're after.

Hi Ray, I think the problem lies with the URL encoding that's been used, try switching to using a literal ampersand (&) and not %26. curl -u admin:pass -X POST -H "X-Atlassian-Token:nocheck" "https://localhost/rest/api/1.0/admin/users?name=testuse&password=password&displayName=Test+User&emailAddress=test@example.com"…

Hi, Based on that message, I'm guessing that when you start the second node you're prompted to go through the same initial setup and configuration as you did on the first node. This should not be the case as the second node should pick up the configuration from the shared NFS mount. Can you confirm that the nodes all have…

Hi Brian, I would suspect that Bitbucket Server is missing the configuration for the proxy server. Have you updated server.xml to include the proxyName, proxyPort, secure, and scheme attributes as mentioned in Proxying and securing Bitbucket Server? Cheers, Jeff

Hi Sean, If you're running Bitbucket Server 4.12+, this information is included in the repository-config file found in the root of the repository. For example, the contents of the file include: #>***********************************************# THIS FILE IS MAINTAINED BY ATLASSIAN BITBUCKET# IT CONTAINS NO USER-SERVICEABLE…