31 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?
!qa required_data
Thank you for your question. Our support team has noted that your request does not meet the minimum required data so we are unable to answer your question.
Please provide:
- your Homarr logs
- your setup configuration (eg. docker compose, docker run, helm chart, screenshot, ...)
- A detailed description of your problem or question with additional images where necessary
- Your operating system
- Version of Homarr (do not say latest! say 0.15.2, ...)
Failure to comply with this will result in a permanent closure of your support request.
Please also provide what you did (did you migrate from <1.0 to 1.0? Did you start from zero?)
I migrated to 1.0 when it was released and all went fine, today I upgraded to 1.1.0 and now I get the above.
Using unraid app
Did you set the encryption key?
Yes to a new one
Did you ever change the encryption key (eg. when upgrading)?
Yes
You should never change it, it will make all of your secrets unreadable. It is only set on the initial installation and must never be changed afterwards. You must revert to the old encryption key. If you can't (eg. don't remember it), you must start over and delete all integrations (or at least re-set the secrets of them)
I have a backup of my data before upgrading, can I find it there?
I don't know what your backup looks like
So, I don't know
complete backup of the appdata folder
But remember, the encryption key is set as an environment variable, not in the mounted directories.
I see
No, that doesn't work. The encryption key is in an environment variable.
I tried to reset the secrets but I get an "unable to save" error
Log?
This is what I get when trying to save
@Meierschlumpf why do we decrypt when secrets are updated?
@Triiiple please wait for any further replies from our team
Ok will do, thanks
Because we allow partial upgrades, I guess here we should add a try catch then and not reuse the secret when an error occurs
So I have to remove my integrations and re-add them?
So I removed them and re-added them except it won't let me remove or change the Overseerr integration
1. the problem that you can't update the secrets should be reported as an issue so @Meierschlumpf can fix it.
2. I suspect there is still a search engine referencing it. Can you try to delete that first? If this fixes it, then this is another bug which you can submit a new issue for.
it won't let me delete that search engine
Please report both issues on GitHub. This is likely a bug on our side
Ok, just reported them