[NV-2220] 🐛 Bug Report: Novu account get reset after some interval

[IXBalaji]

📜 Description

We have set up the Novu development on aws ec2. we have observed every morning that our Novu account of the user is getting reset.
We assigned our domain for the Novu frontend, API, and socket and set up the nginx reverse proxy. All other containers are running on localhost.
we are observing this issue since last week . every day we need to create new user and set all the templates and workflow again.
Your response is appreciated.

👟 Reproduction steps

set up novu user account . come back on next day. hit frontend url. on login with correct credentials its shows account not found.

👍 Expected behavior

User account should not get reset automatically

👎 Actual Behavior with Screenshots

Every morning we need to create new user account on Novu.

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit PR?

None

_NV-2220

[scopsy]

Hi @IXBalaji it seems like you are not persisting your MongoDB server instance or it's storage. How are you running or managing your Mongo server? cc. @jainpawan21

[scopsy]

Would suggest posting this on our discord support channel aswell: https://discord.novu.co/

[IXBalaji]

Hi @scopsy MongoDB server and storage is running on localhost on same server.

[scopsy]

@IXBalaji could you please elaborate a bit more on how did you run MongoDB? What was the starting command, and how are you ensuring persistency on the hard disk there?

[IXBalaji]

@scopsy I have cloned code from repo with this command git clone --depth 1 https://github.com/novuhq/novu.
Then followed following commands to set up the Environment .

Go to the docker folder

cd novu/docker

Copy the example env file

cp .env.example ./local/deployment/.env

Start Novu

docker-compose -f ./local/deployment/docker-compose.yml up.
Once all containers are up and running, I have added nginx reverse proxy for port 4200,3000,3002.
I have not did anything special to MongoDB instance.
Please give a steps to persist the storage and mongo instance.

[christiantobin]

I am experiencing the same issue. Deployed Novu to an EC2 instance with Docker. I'm thinking of moving my database to DocumentDB to avoid this issue.

[slobos]

I am having the same issue as well, is there any workaround or fix this problem, I will really appreciate any input about it.

[christiantobin]

Hi @slobos. I know this isn't a solution for everyone, but we ended up ditching the self-hosted mongodb volume because of this issue and are now pointing our novu project to a dedicated DocumentDB instance. Haven't had the issue since. Definitely seems like an issue with the volume not persisting even if configured to do so.

[slobos]

Hi @slobos. I know this isn't a solution for everyone, but we ended up ditching the self-hosted mongodb volume because of this issue and are now pointing our novu project to a dedicated DocumentDB instance. Haven't had the issue since. Definitely seems like an issue with the volume not persisting even if configured to do so.

Many thanks @christiantobin , glad to hear that there's a workaround, I'll give it try, thanks for your reply!

[Cliftonz]

Thank you for the information on this. We will be updating our documentation to include this.

If you have this issue in the future please create a new issue.