-
Notifications
You must be signed in to change notification settings - Fork 11
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
An error occurred in the Zilean setup: 'NoneType' object has no attribute 'lower' #54
Comments
If you want to disable Zilean, ensure that |
I think it wasn't Zilean after all. I disabled it via your instruction, and then I got a different error:
which lead me to replace my Riven settings.json, which allowed Riven to successfully start. Very strange, I didn't change anything in it to cause the issue. Anyway I'll close this out! |
This was probably related to the latest Riven backend release; it required resetting the database and settings in most instances. Your original issue was related to ZILEAN_UPDATE not being enabled and is now resolved in Version [5.1.9] |
Oh interesting, I wasn't aware of the Riven backend update. I'll subscribe to that channel so I can keep track of changes proactively. And thanks for the heads up and fixing the other issue too. |
Describe the bug
I've been using DMB/Riven for the past couple weeks successfully. But something happened to my setup in the past day or two, I just realized it today. I haven't made any changes manually that would've caused this to my knowledge.
I've attached the error log below. It appears that the log states "ERROR - An error occurred in the Zilean setup: 'NoneType' object has no attribute 'lower'" and then immediately after it says "INFO - Shutdown signal received. Cleaning up..."
I had Zilean enabled at one point, but I actually disabled it in the Riven settings.json file, and this is still happening.
Any idea what I should do to resolve this?
Please complete the following information:
OS: Proxmox LXC with only Portainer/Docker.
Version: Portainer 2.21.0 Community Edition (self-hosted)
Supporting Applications:
Error log:
The text was updated successfully, but these errors were encountered: