[BUG]: When creating custom login on onboarding-setup page I get the error "System setup has already been completed - you cannot do this again." #72

New Issue

2026-02-15T16:30:00-05:00

yindo commented

2026-02-15 16:30:00 -05:00

Originally created by @sfstw on GitHub (Apr 24, 2024).

Originally assigned to: @timothycarambat on GitHub.

How are you running VectorAdmin?

Docker (local)

What happened?

I have used your fantastic tool before and it used to work. This is why it's even more frustrating.

When I use some random email and "password" as password to create a custom login I get this error message

Error creating login: [000] System setup has already been completed - you cannot do this again.

Are there known steps to reproduce?

This is my .env file:

JWT_SECRET="some-random-string"
INNGEST_SIGNING_KEY="some-random-string"
DATABASE_CONNECTION_STRING="postgresql://vectoradmin:password@host.docker.internal:5433/vdbms"

I run docker-compose up -d --build vector-admin and when its finished I open http://localhost:3001/ and I get redirected to http://localhost:3001/onboarding-setup.

The UI is new and it says "Create your custom login". When I use some random email and "password" as password to create a custom login I get this error message

Error creating login: [000] System setup has already been completed - you cannot do this again.

I tried deleting the container and the images, pulling everything new and spinning them up again. Nothing helped. I'm stuck.

Originally created by @sfstw on GitHub (Apr 24, 2024). Originally assigned to: @timothycarambat on GitHub. ### How are you running VectorAdmin? Docker (local) ### What happened? I have used your fantastic tool before and it used to work. This is why it's even more frustrating. When I use some random email and "password" as password to create a custom login I get this error message ```error Error creating login: [000] System setup has already been completed - you cannot do this again. ``` ### Are there known steps to reproduce? This is my `.env` file: ```env JWT_SECRET="some-random-string" INNGEST_SIGNING_KEY="some-random-string" DATABASE_CONNECTION_STRING="postgresql://vectoradmin:password@host.docker.internal:5433/vdbms" ``` I run `docker-compose up -d --build vector-admin` and when its finished I open `http://localhost:3001/` and I get redirected to `http://localhost:3001/onboarding-setup`. The UI is new and it says "Create your custom login". When I use some random email and "password" as password to create a custom login I get this error message ```error Error creating login: [000] System setup has already been completed - you cannot do this again. ``` I tried deleting the container and the images, pulling everything new and spinning them up again. Nothing helped. I'm stuck.

yindo added the possible bug label 2026-02-15 16:30:00 -05:00

yindo commented

2026-02-15 16:30:00 -05:00

@Parsa-Mir commented on GitHub (Dec 10, 2024):

Hi @sfstw ,

The problem seems to be related to the persistence of the PostgreSQL data directory, which retains the initial system setup information even after recreating containers. Here's a step-by-step solution:

Quick Fix

Change the PostgreSQL volume directory or remove it:
Modify the volumes section in your docker-compose.yml for the postgres service as shown below:
```
services:
  postgres:
    ...
    volumes:
      - ../postgres:/var/lib/postgresql/data
   ...
```
Change ~apps/postgres to something like ../postgresa different directory path

OR Remove the existing volume data by running the following command (if you used the default values, it would look like this):
```
rm -rf ~/apps/postgres
```

Rebuild and Restart the Services:
Run the following commands ( in the docker compose directory):

# remove the currently running containers
docker-compose down  
# Rebuild 
docker-compose up -d --build

Bypass Initial Authentication:
If the system setup persists and it directs you to the /auth/sign-in, you then need to bypass the initial authentication by using the root credentials defined in the backend boot script (vectordb/vector-admin/backend/utils/boot/index.js):
- Email: root@vectoradmin.com
- Password: password

This should allow you to log in and proceed without encountering the "System setup has already been completed" error.

@timothycarambat please correct me if I was wrong.

@Parsa-Mir commented on GitHub (Dec 10, 2024): Hi @sfstw , The problem seems to be related to the persistence of the PostgreSQL data directory, which retains the initial system setup information even after recreating containers. Here's a step-by-step solution: ## Quick Fix 1. **Change the PostgreSQL volume directory or remove it**: Modify the `volumes` section in your `docker-compose.yml` for the `postgres` service as shown below: ```yaml services: postgres: ... volumes: - ../postgres:/var/lib/postgresql/data ... ``` Change `~apps/postgres` to something like `../postgres`a different directory path <br/><br/> **OR** Remove the existing volume data by running the following command (if you used the default values, it would look like this): ```bash rm -rf ~/apps/postgres ``` 2. **Rebuild and Restart the Services**: Run the following commands ( in the docker compose directory): ```bash # remove the currently running containers docker-compose down # Rebuild docker-compose up -d --build ``` 3. **Bypass Initial Authentication**: If the system setup persists and it directs you to the /auth/sign-in, you then need to bypass the initial authentication by using the root credentials defined in the backend boot script (`vectordb/vector-admin/backend/utils/boot/index.js`): - Email: `root@vectoradmin.com` - Password: `password` This should allow you to log in and proceed without encountering the "System setup has already been completed" error. @timothycarambat please correct me if I was wrong.

yindo referenced this issue

2026-02-15 16:30:23 -05:00

[PR #72] [MERGED] Fix org deletion redirection path #129

yindo referenced this issue

2026-02-23 17:21:06 -05:00

[PR #72] [MERGED] Fix org deletion redirection path #286

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Mintplex-Labs/vector-admin#72