I am trying to re-host our old bitbucket server from CentOS to Red Hat Enterprise.
Currently the web interface comes up with the user ID I created for postgresql saying sorry no access with that user ID.
The old system did not have access for bitbucket server to postgresql (version 10).
The new system will have a password for access for all users of postgresql (Version 11).
pgadmin4 - can't be installed at this time. Stuff is locked down and I am working to get this tool among others installed back on the new server.
What file do I need to update on the bitbucket server side to edit with 'vi' tell the system use this account & password for access to PostgreSQL server?
Summary - to fix - resolve issues I ended up re-installing the same version of PostgreSQL, that way I could copy the old directory from the server and get things working. This way issues with export of PostgreSQL never impacted the server move from Cent OS to Red Hat. Once Bitbucket is happy, snap the VM, and upgrade in place postgreSQL to the version desired.
It's <bitbucket-data-directory>/shared/bitbucket.properties
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
what is the var name?
I had started to add support to this file for SSL - but backed out.
The org system had no password set - so....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You should not be able to miss it - your bitbucket should never get that far without an error saying "properties file missing property x"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I will double check; the first time I checked I did not see that specific error message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
jdbc.password if I got it right - odd - I did update the database with the correct password that matched this entry - same sort of error - time to dig into the postgresql log files.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
follow up - should the passwords be in
jdbc.password = Value1$
jdbc.password = "Value1$"
jdbc.password = 'Value1$'
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.