#Migration on Synology NAS - User issue

48 messages Β· Page 1 of 1 (latest)

modern tundra
#

Good morning. I am going through the migration guide and notice the reference to the "node" user UID:GID 1000. On my NAS I have no such user. Am I missing something here?

somber flame
#

Nope :D, you don't need that user to exist

modern tundra
#

Oh. But I do still need to run chown -R 1000:1000 on the directory I am migrating to?

#

Ok, I got the permissions figured out. Thanks, getting a different issue but I will look into it

river adder
modern tundra
#

Of course, didn't want to bug before I did some basic troubleshooting.. Here is the error

#

Connecting to localhost: 5056 (127.0.0.1:5056) wget: can't connect to remote host (127.0.0.1): Connection

somber flame
#

5056 is an arr app ?

modern tundra
#

I had the old jellyseerr running on 5056

somber flame
#

you changed the port ?

#

because seerr/jellyseerr always used port 5055 as default

modern tundra
#

I don't recall why I did it, but it has been that way since I installed. I can connect to SEERR on 5056 just fine

#

but I am using IP from my PC, not 127.0.0.1

somber flame
#

Have you updated the healthcheck ?

#

you have to update the port here also

#

I think it's your issue πŸ˜„

modern tundra
#

In the install script this is what I did for the health check

somber flame
#

okay if you changed the port that's good

#

what your compose looks like ?

modern tundra
#

docker run -d
--name seerr
--init
-e PUID=1027
-e PGID=100
-e LOG_LEVEL=debug
-e TZ=America/New_York
-p 5056:5055
-v /volume1/docker/seerr:/app/config
--restart unless-stopped
--health-cmd "wget --no-verbose --tries=1 --spider http://localhost:5056/api/v1/status || exit 1"
--health-start-period 20s
--health-timeout 3s
--health-interval 15s
--health-retries 3
ghcr.io/seerr-team/seerr:latest

#

and for the record, I am no docker expert, if that isn't obvious πŸ™‚

somber flame
#

PUID/PGID you can remove that

#

it's useless

#

Okay I got your issue πŸ˜„

#

use 5055 in the healthcheck

#

-p 5056:5055 means

The container inside use port 5055, and it's mapped to the port 5056 on the host

User --- port 5056 ---- Your machine ---- 5055 --- seerr

#

the wget command is run inside the container so you have to use 5055

modern tundra
#

Ok, that makes sense. Let me go ahead and make that change.. I appreciate all the help as well

#

Ok, where do I make that change? In a config file somewhere?

somber flame
#

what ?

#

the wget ?

modern tundra
#

yes

somber flame
#

edit the command you given to me πŸ˜„

modern tundra
#

Ok, got it

somber flame
#

just stop the old container before

#

to avoid having multiple

modern tundra
#

That did it! Thank you for all the help

somber flame
#

your welcome

merry moat
#

How'd you get past the permission issue?

upper badger
#

I am also having the access denied issue with the new 'node' user on Synology. @modern tundra Could you share how you resolved it?

modern tundra
#

I ran the command listed in the migration checklist. the chown -R 1000:1000 on the directory for the node user (that doesn't exist but is used)

upper badger
#

via SSH on the synology you mean?

modern tundra
#

exactly

upper badger
#

I'll give it a go

#

That worked! tyvm

#

@merry moat fyi ^