Hi, I've been running LakeFS on AWS for a couple of months now and it's been serving us great. Yesterday I had to redeploy our whole stack, including the RDS instance that LakeFS is using. The problem is that RDS now generated a password for the database that has a

^

character in it and now I get the following error when starting lakefs:

panic: parse connection string: cannot parse `<postgresql://lakefs>:<password>@lakefs.<url>.<http://us-east-1.rds.amazonaws.com/lakefs|us-east-1.rds.amazonaws.com/lakefs>`: failed to parse as URL (parse "<postgresql://lakefs>:<password>@lakefs.<url>.<http://us-east-1.rds.amazonaws.com/lakefs|us-east-1.rds.amazonaws.com/lakefs>": net/url: invalid userinfo)

Will I have to recreate the database again or is there another way to make this work?

Hi, welcome! we are thrilled to hear that you are enjoying lakefs! We are looking into your issue and will get back to you asap.

@Tal Sofer now I get:

panic: could not open DB: failed to connect to `host=lakefs.<url>.<http://us-east-1.rds.amazonaws.com|us-east-1.rds.amazonaws.com> user=lakefs database=lakefs`: server error (FATAL: password authentication failed for user "lakefs" (SQLSTATE 28P01))

@TheEdgeOfRage just to confirm the steps that you went through - I had the password

pas^

for the

lakefs

user, what I did is changing the db

connection_string

in lakefs config to

<postgres://lakefs>:pas%5E@<host>/<db_name>?sslmode=disable

. after that, the connection was successful. Have you followed the same steps?

I think I found the issue. I made an awk script that did the url encoding for the password, but accidentally had it output an extra \n character at the end of the password which lead to it adding '%0a' to the password. I have fixed the script and it runs just fine now. Thank you for the help and sorry for the false alarm.

Super! No worries at all. Let us know if we can help with anything else