Error after updating (not sure which tag to assign to it)
Hello!
I'll preface this by saying it probably is some very stupid error on my part. It's been a while since I've updated Homarr.
I've updated it through portainer, using recreate with "Re-pull the image".
Now that I've updated it, I get an error page saying "An unexpected error has occurred. - Type: Client side".
When I go to the logs, I get this:
Any idea where should I even start looking for a fix?
Solution:Jump to solution
Actually, I think you might have updated from a pre Auth version. Did you add the mount for the database?
We'll need to check your docker-compose if you did use that....
16 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Hi, what file storage do you use? Is it a SMB mounted share? What does your config look like?
Ahhhh I'm lost there. I'm using a VPS and have no idea there. As for config, I'm fairly sure it was just some default docker-compose from github. I don't have the compose anymore since it was created using an older version of portainer and i didnt know how to keep "permissions" to view/edit the compose file through versions
Solution
Actually, I think you might have updated from a pre Auth version. Did you add the mount for the database?
We'll need to check your docker-compose if you did use that.
Is that Auth version from within the last year?
Cause in that case, I havent. Im using the default password on the front page but thats it
V0.14 from november
ok yeah i might not have updated since lol
Default password was deprecated in favor of a full userbase authentication system
Then again, if i use the latest docker-compose shown on documentation, I shouldn't lose any info as long as I dont delete the volume
or will it?
Do a backup, always best practice. But no you shouldn't
i mean... as you can tell I'm a very newbie... I'm just gonna Leeroy it and if it breaks I'll just re-add things back
It's best if you use the same docker compose as you already have, simply add this line under volumes:
- ./homarr/data:/data
This way you make sure you're not changing the other mounts.You mentioned portainer earlier, maybe this line is more representative:
- <your-path>/data:/data
Just change "<your-path>" to the same paths used on the lines above.
https://homarr.dev/docs/getting-started/installation#-portainer-ce🚀 Installation | Homarr documentation
We provide multiple installation methods. Are you a newbie to Docker? We recommend Docker Compose for beginners.
I dont know which path i've used before, but in any case a fresh start will get me tinkering again
and the volume is still there somewhere (i think) so all good
I've updated it and it does now work. It was that auth issue
Wonderful, make sure to update often, we post announcements here about breaking issues such as those