Admin-Login Opencloud - HTTP Error 500

[duesi31]

Hi,

I installed an opencloud-instance with docker-compose faced to the internet. Everything seams to be ok and I can call the login-page calling the internet-url. But if I want to login as admin (user: admin/pwd like set in the .env-file) I get the error message "Unexpected HTTP response: 500. Please check your connection and try again."
Also activating the demo users was without success. Same error.
docker logs shows following error:
"opencloud {"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 "Invalid Credentials": ","time":"2025-04-27T18:11:18Z","line":"github.com/opencloud-eu/opencloud/pkg/log/logrus_wrapper.go:50","message":"identifier failed to logon with backend"}". I don't know why opencloud try to communigate with ldap ?!
I tried different passwords for admin in the -env-file. Also the rolling and normal-docker-image.

Anybody a hint what is wrong here ?

Daniel

[micbar]

"opencloud {"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 "Invalid Credentials": ","time":"2025-04-27T18:11:18Z","line":"github.com/opencloud-eu/opencloud/pkg/log/logrus_wrapper.go:50","message":"identifier failed to logon with backend"}". I don't know why opencloud try to communigate with ldap ?!

Opencloud needs to store the users somewhere. There is no relational database, so it uses an internal LDAP server, the so-called idm service.

The ldap bind password is created during the opencloud init step and is stored in the opencloud.yaml file.

If that doesn't match, you see the error from above.

@rhafer how can we reset that without running opencloud init again?

[rhafer]

@rhafer how can we reset that without running opencloud init again?

That would be opencloud idm resetpassword --user-name <username> (while opencloud is not running). But that command can currently only set the password of "normal" users.

Unfortunately, the status code 500 indicates that it is not the user's password what is wrong, but one for the services (idp) in this case can't authenticate. We currently don't have a tool for resetting the service passwords unfortunately. That reminds me that we should have a tool to also reset the service passwords to the values specified in the config file (or, if possible, reset them at service startup)

@duesi31 Did you call opencloud init --force-overwrite at some point? Or remove the opencloud.yaml file? That would have reset all the service password in the config without resetting them in the LDAP service, leading to a situation similar to yours.

If you're still in the process of setting things up and don't have any "important" data in your opencloud, the easiest way to solve the issue is to remove the idm service's database and have it regenerate from scratch. (That would of course remove any user you created before)

[duesi31]

Hi Ralf,

many thanks. I'm not aware that I executed the init-command you mentioned. Also I didn't delete the yaml-file.

How can I remove the idm-database and regenerate it?

[rhafer]

There should be a file called idm.boltdb inside the folder idm in the opencloud data directory. If you move that file away and restart opencloud it will create an new empty database and add the services users.

[fimdomeio]

I was having trouble installing open cloud. Was following the instructions at: https://github.com/opencloud-eu/opencloud-compose and tried both without traefik and with traefic. I could get to the login page but then was getting a 500 error and could not proceed.

I solved the issue by removing the idm.boltdb file and then recreating the other containers.

[micbar]

The idm and openCloud is initialized with random passwords and secrets.

If you delete data or config folders or if they are not properly writable during first initialization, you can get this result.

[digitaltom]

I'm running into the same issue even after clearing the /etc/opencloud and /var/lib/opencloud volumes and re-initializing opencloud:

{"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"127.0.0.1:51034","time":"2025-10-18T22:59:01Z","line":"github.com/opencloud-eu/opencloud/pkg/log/logrus_wrapper.go:50","message":"not found"}
{"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\": ","time":"2025-10-18T22:59:01Z","line":"github.com/opencloud-eu/opencloud/pkg/log/logrus_wrapper.go:50","message":"identifier failed to logon with backend"}

Is there a way I can compare the bind password from my opencloud.yaml with the one used by idm?
With boltbrowser, it looks like my idm.boltdb is empty. If I understand you correctly it should initialize automatically with the value from opencloud.yaml?

[micbar]

yes. The idm should initialize the idm.boltdb with the value from the yaml file.

[csaeum]

OpenCloud Login Error 500 - "uid=idp" not found in IDM database

Environment:

• OpenCloud: Latest stable (v4) and rolling tested
• Setup: Docker Compose with external reverse proxy (frp + Traefik on remote server)
• OS: Proxmox LXC container (Debian-based)
• Storage: ZFS datasets (/mnt/opencloud/config and /mnt/opencloud/data)
• Permissions: Correctly set to 1000:1000

Configuration:

COMPOSE_FILE=docker-compose.yml:weboffice/collabora.yml:external-proxy/opencloud.yml:external-proxy/collabora.yml:search/tika.yml
OC_DOCKER_IMAGE=opencloudeu/opencloud
OC_DOCKER_TAG=4
INITIAL_ADMIN_PASSWORD=R5AkbrGQFZaMxsKA
OC_CONFIG_DIR=/mnt/opencloud/config
OC_DATA_DIR=/mnt/opencloud/data
OC_DOMAIN=cloud.web-seo-consulting.eu

Problem:
Login fails with HTTP 500 error. Logs show:

{"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"127.0.0.1","message":"not found"}
{"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\"","message":"identifier failed to logon with backend"}

What we tried:

1. ✅ Complete reset: rm -rf config/* data/* + restart
2. ✅ Manual init: docker compose exec opencloud opencloud init --force-overwrite
3. ✅ IDM database reset: rm idm/idm.boltdb + restart
4. ✅ Switched from opencloud-rolling to stable release v4
5. ✅ Removed special characters from password (initially had !)
6. ✅ Verified permissions (1000:1000 everywhere)
7. ✅ Verified .env variables are correctly passed to container

Findings:

• opencloud init runs successfully and generates config with admin password
• IDM service starts: "starting LDAPS listener" appears in logs
• idm.boltdb file is created (32KB) but appears empty/incomplete
• The service user uid=idp is never created in the IDM database
• Admin user login fails because IDP service cannot authenticate against IDM

Similar issues:

• Discussion Admin-Login Opencloud - HTTP Error 500 #730: https://github.com/orgs/opencloud-eu/discussions/730
• Same error pattern, solution was to delete idm.boltdb, but this doesn't help in our case

Question:
Why is the IDM service not populating the database with service users (uid=idp) during initialization? The database file exists but the LDAP tree structure seems incomplete.

Is there a manual way to verify/force the IDM initialization, or a known issue with external-proxy setups?