Immutable solution version
π Bug Report: Novu Application getting Network Error while getting singup
Complete solution
Shows how to fix π Bug Report: Novu Application getting Network Error while getting singup. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
We have using ingress AWS ALB to expose novu application to public. my env-dev file is π # Secrets # YOU MUST CHANGE THESE BEFORE GOING INTO PRODUCTION JWTSECRET [redacted] STOREENCRYPTIONKEY [redacted] ## General NODEENV=production MONGOURL=XXXXX/novu-db MONGOMAXPOOLSIZE=500 REDISHOST=novu-redis-dev #REDISCACHESERVICEHOST=novu-redis-dev #REDISCACHESERVICE_PORT=6379 # AWS...
Steps
- If self-hosted Novu shows network errors on signup or signin after you changed APIROOTURL, note that Novu writes REACTAPPAPI_URL into MongoDB on first start, so later env changes have no effect (the volume survives docker-compose down). One user fixed it by tearing down, removing the mongodb volume, and starting again with the correct .env. If you are on Kubernetes with an ingress, another user fixed the same symptom by stripping the /api prefix in the ingress rewrite so the API service receives paths like /v1/auth.
When to use
You are seeing this: Issue novuhq/novu#3602 (closed, 36 comments): ### π Description We have deployed novu in Kubernetes environment with provided kustomize deployments files in Novu Documentation. we have facing issue(Network Issue) while getting signup or Sign in to Novu. Use this skill when you run into "π Bug Report: Novu Application getting Network Error while getting singup".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
In the GitHub issue gh:novuhq/novu#3602 (https://github.com/novuhq/novu/issues/3602), the problem reported was: Issue novuhq/novu#3602 (closed, 36 comments): ### π Description We have deployed novu in Kubernetes environment with provided kustomize deployments files in Novu Documentation. we have facing issue(Network Issue) while getting signup or Sign in to Novu. We have using ingress AWS ALB to expose novu application to public. my env-dev file is π # Secrets # YOU MUST CHANGE THESE BEFORE GOING INTO PRODUCTION JWTSECRET [redacted] STOREENCRYPTIONKEY [redacted] ## General NODEENV=production MONGOURL=XXXXX/novu-db MONGOMAXPOOLSIZE=500 REDISHOST=novu-redis-dev #REDISCACHESERVICEHOST=novu-redis-dev #REDISCACHESERVICEPORT=6379 # AWS... The verified resolution was: If self-hosted Novu shows network errors on signup or signin after you changed APIROOTURL, note that Novu writes REACTAPPAPIURL into MongoDB on first start, so later env changes have no effect (the volume survives docker-compose down). One user fixed it by tearing down, removing the mongodb volume, and starting again with the correct .env. If you are on Kubernetes with an ingress, another user fixed the same symptom by stripping the /api prefix in the ingress rewrite so the API service receives paths like /v1/auth.
By @issueatlas Β· Version 2 Β· Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_wtiXgq4Af4oXexkJLMzI9Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">π Bug Report: Novu Application getting Network Error while getting singup <span>β Vectle</span></a>