Can´t login after upgrading to SSD with old configuration

Installation
1

Edit: I tracked back to beginning and missed rsync error not copying two files from .storage including auth (which sounds important for logins) :slight_smile:

Rsync failed to copy two files owned by root on the pi. Everything else owned by user why I missed it in first place. Fixed it by setting up rsync with root permission server side when backing up to include all files, also those owned by root.

Thank you for helping out!

Hey all

I could use a little help.

I upgraded my RP4 to SSD from SD-card.

Instead of rpi-clone I wanted a fresh install. So I cleaned installed ‘RP OS bookworm’ coming from RP OS bullseye on SD-card. I use docker compose with HA in a docker container.

After setting up the new OS and Docker I copied my original compose file and my HA folder.

The container builds just fine and I reach the login page but I simply can´t log in. I can confirm from the old SD-card installation I’m using the correct login, but still fails with wrong login.

I tried this several times with the same result. I would expect exact same behaviour as old installation.

Do I need to change something or did I miss some files from the old installation?

2

Did you get .secrets hidden folder inside original
Config folder?

Usually if you move from old storage location to new storage location and copy all files for HA in docker there is no issue assuming no change.

Are you using nginx. If so, the IP change for nginx and trusted_proxies may be the issue

3

Also did you copy the hidden files and folders in your old HA directory?

4

I did cp including hidden folders but I don’t see a .secrets folder in my backup.

I see other hidden folders like .storage. I’m on my new disk atm. but I can start up the SD-card and check if its in my original files.

I would think as well a cp of the config folder would be the same regardless of the new disk and install.

I don’t use nginx.

5

I meant .storage :smiling_face:

6

Yes i did.

7

Ahhhh. that I have :slight_smile:

8

Has the user you are running HA changed? What user/group/permissions do the files have on the new OS.

9

Same username, same password.

I chowned -R folder to me (user).

If I start the container without the backup conf files it gives the new files root/root permissions.

10

One thing I do when these issues occur is run container with empty folder and no files allowing container to create its own files and folders.

I then connect to container and verify file permissions. Usually my files are in place so at same time I may correct permissions issues if they exist

I then restart container with my corrected files in place

Im thinking HA cant see your files. Wrong permissions

EDIT

To be clear i am saying check permissions from containers command line

11

Se solution in the original post edit.