can not open http://xx.x.x.xx:7990/ when restart the server

Binbin Zhao August 23, 2020

A fatal error has occurred

The following problem occurred, which prevents Atlassian Bitbucket from starting:

  • The database, as currently configured, is not accessible.
    FATAL: no pg_hba.conf entry for host "172.17.0.3", user "bitbucketuser", database "bitbucket", SSL on

 

I install bitbucket by https://hub.docker.com/r/atlassian/bitbucket-server/ and the database used is postgresql. bitbucket server connects with postgresql well until I restart the server and use the command docker + start + ID to start the bitbucket container,I cannot access to the address http://xx.x.x.xx:7990 and the error is as above.  I have added 172.17.0.3 to no pg_hba.conf and restart postgresql. 

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 23, 2020

You need to add the correct line for the ip address into the pg_hba.conf file.

You say you have added it, but the error message is saying that you have not, so there must be something wrong with what you have added.  Either it's looking at a different file, or the lines you have added are wrong.

Binbin Zhao August 23, 2020

Thanks for your reply. The following are ip addresses I added, can you help me check what's wrong with them?

 

local all all peer
# IPv4 local connections:
#host all all 10.1.6.26/32 trust
host all all 127.0.0.1/32 md5
host all all 10.1.6.26/32 md5
host all all 172.17.0.2/32 md5
host all all 172.17.0.3/32 md5
#host all all localhost trust
# IPv6 local connections:
host all all ::1/128 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
local replication all peer
host replication all 127.0.0.1/32 md5
host replication all ::1/128 md5

Binbin Zhao August 23, 2020

Thanks for your help, when I close the bitbucket (docker stop bitbucket) and reopen it, everything looks fine now.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events