I have OpenProject Community Edition 15.5.0 in one Ubuntu virtual machine and Postgres in a different Ubuntu VM. The Postgres VM is running Postgres 13 on port 5432 and Postgres 15 on port 5439. It's Postgres 15 that is being used for the OpenProject database.

OpenProject is working fine. The problem (really just an annoyance) is that every 15 seconds or so it looks for its database in the wrong Postgres cluster. So I see lines in the log file for Postgres 13 (the one that isn't hosting the OP database) like this:

2025-04-23 11:22:37.333 EDT [1415657] openproject@openproject FATAL:  database "openproject" does not exist
2025-04-23 11:22:52.069 EDT [1415706] openproject@openproject FATAL:  database "openproject" does not exist
2025-04-23 11:23:07.011 EDT [1416026] openproject@openproject FATAL:  database "openproject" does not exist
2025-04-23 11:23:21.897 EDT [1416086] openproject@openproject FATAL:  database "openproject" does not exist
2025-04-23 11:23:36.863 EDT [1416145] openproject@openproject FATAL:  database "openproject" does not exist

It apparently finds Postgres 15 just fine, because everything works. It just keeps wanting to talk to the Postgres on the default port (Postgres 13 in my case).

I'm looking for any suggestions about how this behavior could be stopped. Thank you!