Facing an issue with keep Web UI - showing 500 Internal server error

[prasanna-digiedze]

Hi Keep Team,

I ran keep front end and back end after building images from the dev environment ( Dockerfile.dev.ui and Dockerfile.dev.api) and able to spin off containers from the images. Both the services are running at ports: 8080 and 3000 respectively.

While I tried to launch the Web UI at : http://localhost:3000, it's failing with 500 - Internal server error.

Initially I thought it might be due to Authentication and I disabled by setting up the env variable: AUTH_TYPE=NO_AUTH in the build script. Even after that the same issue happens.

The front-end server logs contain following error:

_Error: No valid session or access token found
getHeaders() {

42 | if (!this.session || !this.session.accessToken) {

43 | throw new Error("No valid session or access token found");
| ^
44 | }_

Since we are still trying to setup basic things and play around, we want to start with No Authorization and later plugin User management.

Any documentation or a quick fix to solve this issue so that we could continue forward?

Thanks,
Prasanna

[dosubot[bot]]

To run Keep with no authentication, set the environment variable AUTH_TYPE=NOAUTH (or NO_AUTH, which is mapped internally) for both the frontend and backend containers. This disables login and API key checks for local development (source, code reference).

However, even in no-auth mode, the frontend still expects a session object (either a real user or a GuestSession) before making API requests. If a component tries to use the API before the session is established, you’ll see the “No valid session or access token found” error and a 500 error in the UI (code reference).

Here’s what to check:

• Make sure both containers have AUTH_TYPE=NOAUTH (or NO_AUTH) set in their environment.
• If you made code changes, rebuild your images and restart the containers so the env vars are picked up (source).
• Ensure the frontend waits for the session status to be 'authenticated' or 'unauthenticated' before calling any API hooks or making requests. If you’re customizing the UI, avoid calling useApi or similar hooks during SSR or before the session is ready (code reference).
• If you’re running in Docker, make sure the backend is fully up before the frontend tries to connect.

If you still see the error, check for any frontend code that might be calling API methods before the session is set, or for issues with localStorage access in server-side contexts (related issue).

Let me know if you need a sample docker-compose snippet or more detailed troubleshooting steps!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}