Signup process #1453

New Issue

GiteaMirror · 2026-03-22T17:29:00-05:00

GiteaMirror commented

2026-03-22 17:29:00 -05:00

Originally created by @unbekanntes-pferd on GitHub (Oct 24, 2025).

Hi,

I'm having the same issue as #754 - set up everything via docker compose and MongoDB, used the sign up button, entered username and password.
Login succeeds, error: user not enabled.

Based on https://github.com/moghtech/komodo/blob/main/config/core.config.toml#L151 it says:

## New users will be automatically enabled when they sign up.
## Otherwise, new users will be disabled on first login.
## The first user to login will always be enabled on creation.
## Env: KOMODO_ENABLE_NEW_USERS
## Default: false
enable_new_users = false

I am confused to say the least - users are automatically enabled when they sign up? I guess not. It's also the default. Additionally, I'm definitely the first user togin - still: user disabled.
The documentation on https://komo.do/docs/setup is also not really helpful.

What am I missing?

Thanks

Originally created by @unbekanntes-pferd on GitHub (Oct 24, 2025). Hi, I'm having the same issue as #754 - set up everything via docker compose and MongoDB, used the sign up button, entered username and password. Login succeeds, error: user not enabled. Based on https://github.com/moghtech/komodo/blob/main/config/core.config.toml#L151 it says: ``` ## New users will be automatically enabled when they sign up. ## Otherwise, new users will be disabled on first login. ## The first user to login will always be enabled on creation. ## Env: KOMODO_ENABLE_NEW_USERS ## Default: false enable_new_users = false ``` I am confused to say the least - users are automatically enabled when they sign up? I guess not. It's also the default. Additionally, I'm definitely the first user togin - still: user disabled. The documentation on https://komo.do/docs/setup is also not really helpful. What am I missing? Thanks

GiteaMirror closed this issue

2026-03-22 17:29:01 -05:00

GiteaMirror commented

2026-03-22 17:29:02 -05:00

@mbecker20 commented on GitHub (Oct 24, 2025):

Are you sure that there isn't another user in the database which you made before? This is a very well tested flow, just note the database needs to be "fresh" (uninitialized / no data). You can try recreating the database, or using another KOMODO_DATABASE_DB_NAME. Maybe before messing with your Prod setup, try running a new Core in a VM to make sure all your settings work in a simple environment.

If you want additional users to be enabled when they sign up automatically, you need to change enable_new_users = true. The default is in fact false, as is shown in the snippet you pasted.

@mbecker20 commented on GitHub (Oct 24, 2025): Are you sure that there isn't another user in the database which you made before? This is a very well tested flow, just note the database needs to be "fresh" (uninitialized / no data). You can try recreating the database, or using another `KOMODO_DATABASE_DB_NAME`. Maybe before messing with your Prod setup, try running a new Core in a VM to make sure all your settings work in a simple environment. If you want additional users to be enabled when they sign up automatically, you need to change `enable_new_users = true`. The default is in fact `false`, as is shown in the snippet you pasted.

GiteaMirror commented

2026-03-22 17:29:03 -05:00

@unbekanntes-pferd commented on GitHub (Oct 25, 2025):

Yes - it's a clean install using docker compose on a completely blank device (fwiw: Zimaboard 2 / Ubuntu Server LTS).
I just nuked MongoDB (removed the docker volumes) for a restart - same behavior.
I go to the login page, enter username and password, click sign up - result: user not enabled.

@unbekanntes-pferd commented on GitHub (Oct 25, 2025): Yes - it's a clean install using docker compose on a completely blank device (fwiw: Zimaboard 2 / Ubuntu Server LTS). I just nuked MongoDB (removed the docker volumes) for a restart - same behavior. I go to the login page, enter username and password, click sign up - result: user not enabled.

GiteaMirror commented

2026-03-22 17:29:04 -05:00

@unbekanntes-pferd commented on GitHub (Oct 25, 2025):

Solved

Root cause: did not read compose.env properly - the first admin is not the one I clicked when using the signup process but the default admin user that is set up.
This is obviously my fault - still I think it would help to clarify this in the documentation here:

https://komo.do/docs/setup

Core should now be accessible on the specified port and navigating to http://
: will display the login page. Enter your preferred admin username and password, and click "Sign Up", not "Log In", to create your admin user for Komodo. Any additional users to create accounts will be disabled by default, and must be enabled by an admin.

This is misleading, as it suggests the admin creation process by default requires this signup process, even though it's created automatically if not explicitly commented out in the .env file.

@unbekanntes-pferd commented on GitHub (Oct 25, 2025): Solved Root cause: did not read compose.env properly - the first admin is not the one I clicked when using the signup process but the default admin user that is set up. This is obviously my fault - still I think it would help to clarify this in the documentation here: https://komo.do/docs/setup > Core should now be accessible on the specified port and navigating to http://<address>:<port> will display the login page. Enter your preferred admin username and password, and click "Sign Up", not "Log In", to create your admin user for Komodo. Any additional users to create accounts will be disabled by default, and must be enabled by an admin. This is misleading, as it suggests the admin creation process by default requires this signup process, even though it's created automatically if not explicitly commented out in the .env file.

GiteaMirror commented

2026-03-22 17:29:06 -05:00

@mbecker20 commented on GitHub (Oct 25, 2025):

@unbekanntes-pferd yes the env initialization is newer feature to streamline even more, later releases will update the docs

@mbecker20 commented on GitHub (Oct 25, 2025): @unbekanntes-pferd yes the env initialization is newer feature to streamline even more, later releases will update the docs

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#1453