@greywire this is fixed in the most recent version, see the release notes here. I'll do my best to explain. It seems when Bitnami built these packages they did the initial setup of the instance with one app_key, which was then cached. But then a different app_key was written to the .env file. This key is required for all two way hashing (such as service usernames and password that are stored in the system database.) In order for the the system to be able to lookup the username and password of your external sql database (for example) it has to have the key.
Best practices have us clearing the cache everytime we make changes to .env file or update code, so now the correct cached key has been deleted, and the one that is in the .env file is not usable for retrieving hashed data values. This causes the admin app to start behaving erratically.
To fix this you would need to delete any hashed passwords or user lookups associated with your services or you can simply move to the fix version mentioned in the release notes.