First time logging in to Karrio Dashboard

[wonderbear]

I know this question was posted earlier, but there was no answer posted. I have set up my Karrio dashboard, but when I try to log in using the default admin credentials, they do not work. How can I log in for the first time?

[Ansh-Dev-Nagar]

Hi @wonderbear,

Did you run the command:

karrio createsuperuser

(as mentioned in the setup guide — https://www.karrio.io/docs/developing/local-development)?

This command will prompt you to create admin credentials that can be used to log in later.

If using other setup method or the issue still persists after that, please let me know:

• Which setup method you followed from the documentation?
• Which operating system you’re using?

I’ll try to help you out.

[wonderbear]

Hi Ansh,

No, I did not run that command. I set up Karrio using Google Cloud Run via the Google Cloud UI.

peter

[wonderbear]

Can it be run using an environmental variable or would I have to enter Google CloudShell? I did try setting the ADMIN_EMAIL and ADMIN_PASSWORD variables, but not sure that they apply to the Dashboard. That did not work, however.

[Ansh-Dev-Nagar]

Hi @wonderbear

Thanks for the details!

Just to confirm, did you set it up using the GCP deployment method mentioned here?
https://www.karrio.io/docs/self-hosting/gcp

Also, did you try logging in with these default credentials?
Email: admin@example.com
Password: demo

That’ll help me understand how your setup is configured.

[wonderbear]

I was not able to use the documentation provided for GCP because I did not set it up in a VM. I used Google Cloud Run so that it is in a serverless environment and only runs when needed. I did try those default credentials, yes.

The docker image I pointed to in order to create the container was 'docker.io/karrio/dashboard:latest' if that helps.

[Ansh-Dev-Nagar]

Thanks for the info, @wonderbear!

Got it, I’ll check on this and get back to you soon.

[wonderbear]

Ok, thank you!

[Ansh-Dev-Nagar]

Hi @wonderbear

Thanks for your patience!

You can try resetting your PostgreSQL database and then setting up the following environment variables (as mentioned here: Environment Variables) before redeploying your container:

Variable	Description	Default	Required
ADMIN_EMAIL	Admin user email	admin@example.com	No
ADMIN_PASSWORD	Admin user password	demo	No

Since you’re using the Docker image, the dashboard should automatically create the superuser using these environment variables on startup.

After redeploying, please also check the container logs to confirm that the image starts successfully and that the superuser creation process runs as expected.

[wonderbear]

@danh91 Was that information useful at all?

[wonderbear]

After adding the database env variables, I did see that there were some new tables added, one of them user_user. It has one entry with an email of admin@example.com but a different password from the default. I changed the email and password and I still am not able to log in?

[danh91]

@wonderbear, how did you change the password? The first password that you had in the database successfully migrated should be the password that would be applied.

You can try deleting the user in the database and restarting the server. I suggest using a simple password without any characters that could be an issue as env variable. Something simple like demo, and once you are able to log in to the admin API, you will be able to replace it with a better one.

Another issue that comes to mind could have to do with HTTPS configuration. Is your deployment setup with an HTTPS domain?
When you are using HTTPS domain here are some env var requirements

If DEBUG_MODE is False, you need to set USE_HTTPS to True as well
If DEBUG_MODE is True (Not recommended for production) USE_HTTPS can stay False

Then try restarting the server and attempting to login to the URL http://your.apidomain.com/admin

[danh91]

I made a correction

 If `DEBUG_MODE ` is `False`, you need to set `USE_HTTPS` to `True` as well
 If `DEBUG_MODE` is `True` (Not recommended for production) `USE_HTTPS` can stay `False`  

[wonderbear]

@danh91 Ok, tried adding DEBUG_MODE and USE_HTTPS and that seemed to work. I deleted the user in the database and then added those fields to the api container and I was able to log in. Thank you!