We could not log you in - contact an admin. [002] Failed to authenticate (First time login) #182

Closed
opened 2026-02-23 17:20:40 -05:00 by yindo · 4 comments
Owner

Originally created by @umair313 on GitHub (Sep 7, 2023).

Following this https://github.com/Mintplex-Labs/vector-admin/blob/master/docker/DOCKER.md#how-to-install

and then using default Sys email and password I get this error unable to login
I tried with cridentials in docker/.env and backend/.env both didn't work
Logs

2023-09-07 14:42:35 Warning: connect.session() MemoryStore is not
2023-09-07 14:42:35 designed for a production environment, as it will leak
2023-09-07 14:42:35 memory, and will not scale past a single process.
2023-09-07 14:42:35 Warning: connect.session() MemoryStore is not
2023-09-07 14:42:35 designed for a production environment, as it will leak
2023-09-07 14:42:35 memory, and will not scale past a single process.
2023-09-07 14:42:34 SELECT * FROM system_settings WHERE label = 'telemetry_id'
2023-09-07 14:42:34 [TELEMETRY SENT] { event: 'server_boot', properties: { commit: '--' } }
2023-09-07 14:42:34 SELECT COUNT(*) as count FROM users WHERE role = "admin"
2023-09-07 14:42:34 SELECT * FROM users WHERE email = 'root@example.com' AND role = 'root'
2023-09-07 14:42:34 INSERT INTO users (email, password, role) VALUES ('root@example.com', '$2b$10$8QuMQU8wveRP2.CNVlbT7eMynhAPu0NvIAc.6Ak6tdOGNjmKEesla', 'root')
2023-09-07 14:42:34 Root user created with credentials
2023-09-07 14:42:34 Example app listening on port 3001
2023-09-07 14:42:34 SELECT * FROM system_settings WHERE label = 'debug_username'
2023-09-07 14:42:35 setupFunctions success! 200
2023-09-07 14:42:35 Background workers listening on port 3355

Originally created by @umair313 on GitHub (Sep 7, 2023). Following this https://github.com/Mintplex-Labs/vector-admin/blob/master/docker/DOCKER.md#how-to-install and then using default Sys email and password I get this error unable to login I tried with cridentials in docker/.env and backend/.env both didn't work Logs 2023-09-07 14:42:35 Warning: connect.session() MemoryStore is not 2023-09-07 14:42:35 designed for a production environment, as it will leak 2023-09-07 14:42:35 memory, and will not scale past a single process. 2023-09-07 14:42:35 Warning: connect.session() MemoryStore is not 2023-09-07 14:42:35 designed for a production environment, as it will leak 2023-09-07 14:42:35 memory, and will not scale past a single process. 2023-09-07 14:42:34 SELECT * FROM system_settings WHERE label = 'telemetry_id' 2023-09-07 14:42:34 [TELEMETRY SENT] { event: 'server_boot', properties: { commit: '--' } } 2023-09-07 14:42:34 SELECT COUNT(*) as count FROM users WHERE role = "admin" 2023-09-07 14:42:34 SELECT * FROM users WHERE email = 'root@example.com' AND role = 'root' 2023-09-07 14:42:34 INSERT INTO users (email, password, role) VALUES ('root@example.com', '$2b$10$8QuMQU8wveRP2.CNVlbT7eMynhAPu0NvIAc.6Ak6tdOGNjmKEesla', 'root') 2023-09-07 14:42:34 Root user created with credentials 2023-09-07 14:42:34 Example app listening on port 3001 2023-09-07 14:42:34 SELECT * FROM system_settings WHERE label = 'debug_username' 2023-09-07 14:42:35 setupFunctions success! 200 2023-09-07 14:42:35 Background workers listening on port 3355
yindo added the question label 2026-02-23 17:20:40 -05:00
yindo closed this issue 2026-02-23 17:20:41 -05:00
Author
Owner

@timothycarambat commented on GitHub (Sep 8, 2023):

If you are using the dockerized instance you should be using the docker/.env credentials. Defaults are:

SYS_EMAIL="root@vectoradmin.com"
SYS_PASSWORD="password"

However, looks like the ENV was read properly as process.env.SYS_EMAIL = process.env.SYS_EMAIL ?? "root@vectoradmin.com"; if unset would have fallen back to root@vectoradmin.com! So it for sure read the correct username. The password for default env file was hunter2. It is case-sensitive. Is this issue still impacting you?

@timothycarambat commented on GitHub (Sep 8, 2023): If you are using the dockerized instance you should be using the `docker/.env` credentials. Defaults are: ``` SYS_EMAIL="root@vectoradmin.com" SYS_PASSWORD="password" ``` However, looks like the ENV was read properly as `process.env.SYS_EMAIL = process.env.SYS_EMAIL ?? "root@vectoradmin.com";` if unset would have fallen back to `root@vectoradmin.com`! So it for sure read the correct username. The password for default env file was `hunter2`. It is case-sensitive. Is this issue still impacting you?
Author
Owner

@umair313 commented on GitHub (Sep 9, 2023):

@timothycarambat Thanks the issue is resolved. after re-cloning the repo.

@umair313 commented on GitHub (Sep 9, 2023): @timothycarambat Thanks the issue is resolved. after re-cloning the repo.
Author
Owner

@mascreativelabs commented on GitHub (Dec 30, 2023):

Hi guys, I hope everyone is doing well.

I am having the same problem.
I tried the solution previously listed

SYS_EMAIL="root@vectoradmin.com" SYS_PASSWORD="password"

but it didn't work how did @umair313 get it to work?

@mascreativelabs commented on GitHub (Dec 30, 2023): Hi guys, I hope everyone is doing well. I am having the same problem. I tried the solution previously listed `SYS_EMAIL="root@vectoradmin.com" SYS_PASSWORD="password"` but it didn't work how did @umair313 get it to work?
Author
Owner

@mascreativelabs commented on GitHub (Dec 30, 2023):

also tried

SYS_EMAIL="root@vectoradmin.com" SYS_PASSWORD="hunter2"

no luck there either

@mascreativelabs commented on GitHub (Dec 30, 2023): also tried `SYS_EMAIL="root@vectoradmin.com" SYS_PASSWORD="hunter2"` no luck there either
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/vector-admin#182