hatchet-lite doesnt seem to be setting up properly. about hatchet

[mattrochon]

Confirmed works, was user-error all along, thanks for the help!

[abelanger5]

Hey @mattrochon, taking a look at this. There's a chance the migration ran on a previous startup of the container, are there any logs further up when you click into the hatchet-lite-hatchet-lite-1 container on docker desktop (or via docker logs...)?

everything looks like it starts up but I am unable to log in.

What do you see when you try to log in? There should be an associated error log here as well.

[mattrochon]

There are a significant amount of logs.

1. Postgres startup, seems to be ok, though I did have to add PGUSER to the env in the yaml file
2. Rabbit MQ startup - it seems to error our tryign to connect to rmq first, then decides its not runnign and starts it up
3. After rmq starts then it checks the db. THe prisma migrations table doesnt exist yet, so no migrations would have been run, assuming that the atlas migrations still updates the prisma table.

the atlas-apply script seems to suggest that it does.

[abelanger5]

Thanks for the additional info. A couple other questions:

1. Seeing Please provide valid credentials is expected, since we check GET /api/v1/users/current when you load localhost:8080. What are the logs when you try to log in with:

   Email: [email protected]
   Password: Admin123!!
   

2. To address this:

   THe prisma migrations table doesnt exist yet, so no migrations would have been run, assuming that the atlas migrations still updates the prisma table.

   The atlas migrations don't update the prisma table - this case should only be hit if you're upgrading from an older version of Hatchet (pre-0.31.0).

   One way we can check if the migrations ran is by adding:

   services:
     postgres:
       # ... rest of config
       ports:
         - "5432:5432"
   # ... rest of config

   And then running psql 'postgresql://hatchet:hatchet@localhost:5432/hatchet', and inside of the shell, run \dt and let me know what it outputs?

[mattrochon]

You're right, looks like the db was created.

THe error message is the exact same when i try to log in. No error appears on the page, only in the logs.

The default user also appears to exist.

[mattrochon]

OK i think the issue is i'm not running it on localhost. I have it running in a remote docker host on my local network.

[abelanger5]

Ah, yeah the cookie has a domain attribute set to localhost. You can change the value of SERVER_AUTH_COOKIE_DOMAIN in the configuration and see if that helps?