-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Bug Report: Novu after Update not usable any more - stuck at auth/application #6144
Comments
@alexanderhofstaetter had a terrible time with this problem as well today, don't know if you found any solution, but I found a solution. In my case, im setting up my self hosted novu for the first time with k8s and i've made the same mistake to use the My solution was to set ALL pods to fetch the Each service would use something like
the only one that I didn't find the hope this helps you or someone else |
@SokratisVidros how can you close this as "not planned" - the feedback on the issues here from novu is terrible, and most of them simple do not get even an answer. Far away from open source IMHO. |
@alexanderhofstaetter, this tag came from an automatic integration we have with Linear. We are in the process, of building our roadmap until the end of the year, including a new release for Novu V2 docker images that is planned to happen by the end of this month. That being said, the pending v2.0 docker image release should address this and similar issues. Using the latest |
📜 Description
After upgrading to the latest version of novu (docker tag prod - as of today) we cannot log in because we are stuck at:
👟 Reproduction steps
👍 Expected behavior
It should let me log in.
👎 Actual Behavior with Screenshots
no errors in network, no errors in console
Novu version
novu selfhosted
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: