after upgrade from 1.33 to 1.43 using portainer all settings and board disappear
after upgrade from 1.33 to 1.43 using portainer all settings and board disappear
Solution:Jump to solution
Our team noticed that you are using the new version of Homarr (>1.0.0) with the mounting points of the legacy version (<=0.16.0).
This is an issue, because Homarr 1.0 and after is relying on the new paths to be mounted and persisted.
To rectify, please follow the following steps:
- Immideatly backup the exported JSON from your legacy Homarr or copy all mounted directories to another host.
...
10 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?
Running on ubuntu using docker managed by portainer with thsee settings in the custom template:
version: '3'
#---------------------------------------------------------------------#
Homarr - A simple, yet powerful dashboard for your server. #
#---------------------------------------------------------------------#
services:
homarr:
container_name: homarr
image: ghcr.io/homarr-labs/homarr:latest
restart: unless-stopped
environment:
- DEFAULT_COLOR_SCHEME=dark
- SECRET_ENCRYPTION_KEY=96681fcb162a97742a6587a426c32800805a5902cc # <--- can be generated with
ports: - '7575:7575'
openssl rand -hex 32
volumes:
- /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
- /opt/homarr/configs:/app/data/configs
- /opt/homarr/icons:/app/public/icons
- /opt/homarr/data:/dataports: - '7575:7575'
!qa leaked_secret_key
Our team noted that at least one of your messages contains a secrets encryption key used in Homarr.
As documented at the installation docs, the secrets encryption key is a cruicial key that will be used to encrypt your data. By posting this key you compromised part of your security and we strongly recommend you to change it, since malicious acters could gain access to your integration passwords, usernames and tokens by decrypting your database if they gain access to said database.
To do this, update the secrets encryption key variable. Doing so will break all integrations and you must manually re-enter the secrets again.
Manually removing it after posting does not fix your issue since automated bots can and will scrape messages for leaked data.
To avoid such problems in the future, please always remove the encryption key when posting online. The Homarr team will never ask you for any passwords or the secrets encryption key.
Docker | Homarr documentation
Docker is our recommended installation method for beginners and professionals.
I renamed the secret key in the config , it is not exactly as it is in ours
!qa legacy_mounts
Solution
Our team noticed that you are using the new version of Homarr (>1.0.0) with the mounting points of the legacy version (<=0.16.0).
This is an issue, because Homarr 1.0 and after is relying on the new paths to be mounted and persisted.
To rectify, please follow the following steps:
- Immideatly backup the exported JSON from your legacy Homarr or copy all mounted directories to another host.
- Follow the upgrade procedure on our blog: https://homarr.dev/blog/2025/01/19/migration-guide-1.0
- Make sure that you no longer have any mounting points for
/app/. /appdata/ is the new point.
- Start your container again and re-import your JSON. To ensure it's working correctly, destroy the container once (e.g. with docker compose down) and re-create it. If everything works, you will not be re-prompted for JSON import.
Please note that Homarr uses https://semver.org/ which indicates such breaking changes using the "major" number increment. Regular backups are strongly recommended. Type "!qa 321" for more information.Issue is fixed now, thank you
Awesome, may I mark this as resolved then?
yes