I am new to Agenta. Really want to try the product. Can't get signed in for the first time after installing.

[gerbpaul]

Thanks in advance for anyone that attempts to help me on this one!

Everything appears to be installed correctly from what I can tell. All containers except the agenta-oss-gh-api-1 container are running. Although even though this container seems to shut down when I attempt to start it in Docker, it does say: 2025-03-20 06:08:51 INFO: Application startup complete.

I read in the bug reports, that when you sign in for the first time, it is supposed to setup an Org and Admin user for you. So I tried that by adding my email and a new password but I just get:

Oops, something went wrong. Please try again
If the issue persists, please contact support

The logs in Docker inside the agenta-oss-gh-api-1 container show:

| 2025-03-20 12:23:23.732521685 | INFO: 172.19.0.4:53604 - "OPTIONS /auth/session/refresh HTTP/1.1" 400 Bad Request
| 2025-03-20 12:23:33.702931708 | INFO: 172.19.0.4:60494 - "OPTIONS /auth/session/refresh HTTP/1.1" 400 Bad Request
| 2025-03-20 12:23:33.788068591 | INFO: 172.19.0.4:60494 - "OPTIONS /auth/session/refresh HTTP/1.1" 400 Bad Request
| 2025-03-20 12:23:33.793508300 | INFO: 172.19.0.4:60494 - "OPTIONS /auth/signup HTTP/1.1" 400 Bad Request

[dosubot[bot]]

Hey @gerbpaul! 👋 I'm here to help you with your Agenta issue. I can assist with bug fixes, answer questions, and even help you become a contributor.

The issue you're experiencing with the "Oops, something went wrong" message during sign-up could be due to several factors. Here are some steps to help you troubleshoot and resolve the problem:

1. Database Migration Issue: Ensure that your database schema is up-to-date. You might need to run a migration command to update the database schema if the 'organizations' table is missing. Use the following command to perform the migration:

   docker exec -e PYTHONPATH=/app -w /app/oss/databases/postgres/migrations agenta-oss-dev-api-1 alembic -c alembic.oss.ini upgrade head

   Also, make sure you are using the correct Docker Compose YAML file that builds the images locally, and consider enabling automatic migrations by setting AGENTA_AUTO_MIGRATIONS=true in your environment configuration ^[1].

2. Check Environment Variables: Verify that all necessary environment variables are correctly set in your .env.oss.gh file. Key variables include database credentials, API keys, and service URLs. Incorrect or missing values can cause the container to fail ^[2].

3. Service Dependencies: Ensure that all dependent services, such as postgres and alembic, are running and healthy. The agenta-oss-gh-api-1 container depends on these services, and they must be operational for it to start correctly ^[3].

4. Network Configuration: Make sure that the network configuration is correct and that all services are part of the same Docker network. This ensures proper communication between services ^[4].

5. Logs and Errors: The logs indicate a 400 Bad Request error for the /auth/session/refresh and /auth/signup endpoints. This could be due to incorrect request formatting or missing required parameters. Double-check the request payloads and ensure they meet the API's requirements.

By following these steps, you should be able to identify and resolve the issue preventing you from signing in. If the problem persists, further investigation into the specific error messages and logs may be necessary.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[mmabrouk]

Thanks @gerbpaul

I am closing the discussion and creating an issue here #2540
Let's continue the discussion there