Mintplex-Labs/vector-admin
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/vector-admin.git synced 2026-07-19 13:16:03 -04:00
Code Issues 79 Packages Projects Releases Wiki Activity

[BUG]: We could not log you in - contact an admin. [002] Failed to authenticate #69

New Issue
Closed
opened 2026-02-15 16:29:58 -05:00 by yindo · 6 comments
yindo commented 2026-02-15 16:29:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @LIdro on GitHub (Feb 13, 2024).

How are you running VectorAdmin?

Local development

What happened?

I cloned your repository to my local environment and followed the installation steps. I am currently facing the failed to authenticate wall. I am using the email: root@vectoradmin.com and password: password
auth-failed-va

Are there known steps to reproduce?

  • I am running it from a windows machine.
  • My postgres instance is also local via pgAdmin. I think vector admin connected properly because it did populate the new database I created for it with the appropriate tables and such.
  • I only changed the DATABASE_CONNECTION_STRING in the .env to suit my use case.
  • I expected vector-admin to run on port 3001 but it automatically opens 3000 instead. I guess this is not an issue.
  • I checked all reported issues, both open and closed but it seems everyone else is running the docker image. I tried to implement suggestions there but it didn't get me anywhere.
  • I tried the docker image but couldn't get passed the long docker run command (docker run -d -p 3001:3001 \ -e SERVER_PORT="3001" ...). Docker told me
    docker: invalid reference format.
    See 'docker run --help'
  • my backend and frontend vector admin commands seem to be running correctly
    frontend-va
    server-va

I am new on reporting issues on github and do not master the format yet. Are there any other details I may need to provide to for the community to help me resolve this issue?

I really want to use this tool. It will cut my dev time by a lot. Please help me out.

Originally created by @LIdro on GitHub (Feb 13, 2024). ### How are you running VectorAdmin? Local development ### What happened? I cloned your repository to my local environment and followed the installation steps. I am currently facing the failed to authenticate wall. I am using the email: root@vectoradmin.com and password: password ![auth-failed-va](https://github.com/Mintplex-Labs/vector-admin/assets/17305111/93c0067f-064f-4c35-8502-e2e5371024ec) ### Are there known steps to reproduce? - I am running it from a windows machine. - My postgres instance is also local via pgAdmin. I think vector admin connected properly because it did populate the new database I created for it with the appropriate tables and such. - I only changed the DATABASE_CONNECTION_STRING in the .env to suit my use case. - I expected vector-admin to run on port 3001 but it automatically opens 3000 instead. I guess this is not an issue. - I checked all reported issues, both open and closed but it seems everyone else is running the docker image. I tried to implement suggestions there but it didn't get me anywhere. - I tried the docker image but couldn't get passed the long docker run command (docker run -d -p 3001:3001 \ -e SERVER_PORT="3001" \...). Docker told me docker: invalid reference format. See 'docker run --help' - my backend and frontend vector admin commands seem to be running correctly ![frontend-va](https://github.com/Mintplex-Labs/vector-admin/assets/17305111/0c19e157-3781-4623-9ac1-cc6adf5ce0a6) ![server-va](https://github.com/Mintplex-Labs/vector-admin/assets/17305111/5c78a4e6-5627-43d3-a4a0-43a1271505ec) I am new on reporting issues on github and do not master the format yet. Are there any other details I may need to provide to for the community to help me resolve this issue? I really want to use this tool. It will cut my dev time by a lot. Please help me out.
yindo added the possible bug label 2026-02-15 16:29:58 -05:00
yindo closed this issue 2026-02-15 16:29:58 -05:00
yindo commented 2026-02-15 16:29:58 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 14, 2024):

Can you open up a database explorer and see if the users table has the admin credential created? Also, can you open the network tab before sending login credentials and ensure that the endpoint requests are being sent to is :3001/api/.. and not :3000/api/...

@timothycarambat commented on GitHub (Feb 14, 2024): Can you open up a database explorer and see if the `users` table has the admin credential created? Also, can you open the network tab before sending login credentials and ensure that the endpoint requests are being sent to is `:3001/api/..` and not `:3000/api/...`
yindo commented 2026-02-15 16:29:58 -05:00
Author
Owner
Copy Link
Copy Source

@LIdro commented on GitHub (Feb 15, 2024):

Can you open up a database explorer and see if the users table has the admin credential created? Also, can you open the network tab before sending login credentials and ensure that the endpoint requests are being sent to is :3001/api/.. and not :3000/api/...

Thanks for the reply.

  • The users table has no records in it
  • As the image below shows, the login request goes to :3000/api/... instead.

I guess this is my problem. Please how can I resolve it?

Thanks for the help so far.

network-tab

@LIdro commented on GitHub (Feb 15, 2024): > Can you open up a database explorer and see if the `users` table has the admin credential created? Also, can you open the network tab before sending login credentials and ensure that the endpoint requests are being sent to is `:3001/api/..` and not `:3000/api/...` Thanks for the reply. - The users table has no records in it - As the image below shows, the login request goes to :3000/api/... instead. I guess this is my problem. Please how can I resolve it? Thanks for the help so far. ![network-tab](https://github.com/Mintplex-Labs/vector-admin/assets/17305111/f38d3d92-3d5c-406d-bd85-07cd7dfd71b9)
yindo commented 2026-02-15 16:29:59 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 15, 2024):

change the value of VITE_API_BASE in frontend/.env to be VITE_API_BASE='http://localhost:3001/api'

@timothycarambat commented on GitHub (Feb 15, 2024): change the value of `VITE_API_BASE` in `frontend/.env` to be `VITE_API_BASE='http://localhost:3001/api'`
yindo commented 2026-02-15 16:29:59 -05:00
Author
Owner
Copy Link
Copy Source

@LIdro commented on GitHub (Feb 16, 2024):

change the value of VITE_API_BASE in frontend/.env to be VITE_API_BASE='http://localhost:3001/api'

Thanks for the response. I will do it and get back to you.

Then what about the absence of the root account in the users table? How can I make the app to create the record? I know it should concern Prisma. I tried entering it manually but the password is not hashed. I guess there should be another way to go about this. Thanks.

@LIdro commented on GitHub (Feb 16, 2024): > change the value of `VITE_API_BASE` in `frontend/.env` to be `VITE_API_BASE='http://localhost:3001/api'` Thanks for the response. I will do it and get back to you. Then what about the absence of the root account in the users table? How can I make the app to create the record? I know it should concern Prisma. I tried entering it manually but the password is not hashed. I guess there should be another way to go about this. Thanks.
yindo commented 2026-02-15 16:29:59 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 16, 2024):

When the system boots up it will attempt to read the users table and auto-create the root account. So unless the database connection string is incorrect then it should automatically do that and enable login!

We will be removing that flow soon with PR https://github.com/Mintplex-Labs/vector-admin/pull/132
So that should simplify things a lot - this detail always causes issues and there are ways to accomplish what it does without making a user that can never been used again

@timothycarambat commented on GitHub (Feb 16, 2024): When the system boots up it will attempt to read the users table and auto-create the root account. So unless the database connection string is incorrect then it should automatically do that and enable login! We will be removing that flow soon with PR https://github.com/Mintplex-Labs/vector-admin/pull/132 So that should simplify things a lot - this detail always causes issues and there are ways to accomplish what it does without making a user that can never been used again
yindo commented 2026-02-15 16:30:00 -05:00
Author
Owner
Copy Link
Copy Source

@LIdro commented on GitHub (Feb 16, 2024):

I have done all I can to get the system to boot.
I have tried placing breakpoints when systemInit() is called, I have stopped and restarted the flask api and the frontend server, all so that I can see if the query to create the user is executed but it does not hit any of my breakpoints.
I have even created another database and called prisma setup to it. It did all but nothing I do auto creates the root user.

I manually created a root user with password encrypted using bcrypt, 10 but it still will not let me in.

Is there something I am missing or could do? Please I really need this vectorAdmin solution.

Thanks.

@LIdro commented on GitHub (Feb 16, 2024): I have done all I can to get the system to boot. I have tried placing breakpoints when systemInit() is called, I have stopped and restarted the flask api and the frontend server, all so that I can see if the query to create the user is executed but it does not hit any of my breakpoints. I have even created another database and called prisma setup to it. It did all but nothing I do auto creates the root user. I manually created a root user with password encrypted using bcrypt, 10 but it still will not let me in. Is there something I am missing or could do? Please I really need this vectorAdmin solution. Thanks.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Docker
UI/UX
UI/UX
bug
bug
core-team
core-team
core-team
documentation
enhancement
enhancement
feature request
good first issue
invalid
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/vector-admin#69
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?