I have just set up a new Bitbucket instance and changed the base URL. I have been able to access the server admin UI via localhost and from a remote machine:
However, I need to access the Bitbucket instance via the URL:
When I attempt to access the web UI via the new base URL, Chrome returns a "connection refused" error, however this does not occur when I use the computer name. Do I need to edit a Tomcat configuration file to allow for the new base URL? I wouldn't think so as I've been able to update the base URL for JIRA and Confluence (separate VMs) without incident.
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 the correct IP address?
Pinging the domain returns the correct IP address as does an nslookup. One would think that if the URL was not pointed to the correct server then it would return a 404 error, as there wouldn't be a URL endpoint configured to accept requests to that URL.
What config file does BitBucket Server edit to specify the URL endpoint? I can manually edit a configuration file if needed. Alternatively, is there a way I can manually re-run the setup process?
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.
The curl result against the desired base URL:
curl: (7) Failed to connect to bitbucket.<domain>.<tld> port 7990: Connection
I know it's to do with the Tomcat instance because I can access the web UI just fine if I use the machine's FQDN. For reference, the machine is on an AD domain and I have pin-point DNS running to have DNS records on their external domain resolving internally. Is there an option in the server.properties file that I can use to specify an alias for Tomcat to accept queries on?
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 would result in the behavior you're seeing.
If the machine name and bitbucket.domain.tld both resolve to the same IP address, then this should all work. The fact that you get a connect refused indicates that there is something amiss with bitbucket.domain.tld and allowing connections through to port 7990.
I receive the same connection error when logged into the server hosting the BitBucket application and connecting to http://localhost:7990/ so that rules out a firewall issue (the firewall is disabled in any case but better safe than sorry). There are no reverse proxies being used.
Which configuration file specifies the address that Tomcat binds to? I might update that to listen on all interfaces.
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.
BitBucket Server is running.
If I browse to http://<machinename>.internal.<domain>.<tld>:7990 I get the logon page, both on the host server and a remote machine.
If I browse to http://localhost:7990 I get a connection refused error.
If I browse to http://bitbucket.<domain>.<tld>:7990 I get a connection refused error.
The firewall is off and the DNS records are pointing to the correct IP address; 192.168.0.43 in this case. I have not exposed the BitBucket server to the outside world as yet, and Active Directory has the required DNS zones so that the DNS zones resolve to the correct locations.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot