-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Description
📜 Description
After setting up a local community edition environment using the official Docker instructions, any operation performed on the main dashboard after logging in results in a generic error message: "Sorry, but something went wrong."
Specifically, this occurs when trying to create a new workflow, add a subscriber, or perform any other main action. The browser's developer console shows two key errors:
Immediately after login: GET http://:3000/v1/organizations/me 422 (Unprocessable Entity)
When performing an action: TypeError: Cannot read properties of undefined (reading 'request')
The provided Event ID for the error is 105be025e75444608f08eb65fcae3bfa.
👟 Reproduction steps
- After setting up a local community edition environment using the official Docker instructions, any operation performed on the main dashboard after logging in results in a generic error message: "Sorry, but something went wrong."
- Specifically, this occurs when trying to create a new workflow, add a subscriber, or perform any other main action. The browser's developer console shows two key errors:
- Immediately after login: GET http://:3000/v1/organizations/me 422 (Unprocessable Entity)
- When performing an action: TypeError: Cannot read properties of undefined (reading 'request')
- The provided Event ID for the error is 105be025e75444608f08eb65fcae3bfa.
👍 Expected behavior
The application should function correctly after a fresh installation. I expected to be able to create new workflows, add subscribers, and use the platform's features without encountering API or client-side errors. The GET /v1/organizations/me call should succeed and return the organization details.
👎 Actual Behavior with Screenshots
The application displays an error banner with the message:
"Sorry, but something went wrong. Please contact our support team and provide the event id for the reference. Event Id: 105be025e75444608f08eb65fcae3bfa."
The browser console shows:
index-CkK80rBX.js:141 GET http://3.110.201.118:3000/v1/organizations/me 422 (Unprocessable Entity)
A subsequent TypeError: Cannot read properties of undefined (reading 'request') when an action is triggered.
sadly i turned the EC2 off and i cant get the dashboard so cant upload the Screenshot.
Novu version
The latest version from the main branch, as installed via git clone --depth 1 on the day of this report.
npm version
N/A - The application is running within the provided Docker containers, not on a local Node installation. The versions are those specified in the project's Dockerfile.
node version
N/A - The application is running within the provided Docker containers. The version is determined by the project's Dockerfile.
📃 Provide any additional context for the Bug.
The root cause appears to be the failing API call to /v1/organizations/me. Because this call fails with a 422 Unprocessable Entity error, the frontend application likely doesn't receive the necessary organization context. This causes subsequent operations (like creating a workflow) to fail with a TypeError because the data they depend on is undefined. The issue seems to be with the initial organization setup or data retrieval immediately after user creation.
👀 Have you spent some time to check if this bug has been raised before?
- I checked and didn't find a similar issue
🏢 Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to submit PR?
Yes I am willing to submit a PR!