I
Immich•4mo ago
jeromecodeium

I can't connect using a rootless setup

I'm new at setting up Immich. I had no issues setting up on MacOS and Ubuntu 24.04 using the normal instructions using docker-desktop Now that I want to run Immich as a "public" server, it seems safer running it docker rootless. However, I can't connect to the port. 😦 All seems to be starting fine and I verified that the docker app is listening on that port: 
lsof -i :2283
COMMAND     PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
rootlessk 37967 jerome   13u  IPv4 210791      0t0  TCP *:2283 (LISTEN)
rootlessk 37967 jerome   16u  IPv6 213520      0t0  TCP *:2283 (LISTEN)
jerome@mac-mini-ubuntu:~/immich-app$ ps -edf |grep 37967
jerome     37967   11719  0 13:51 ?        00:00:00 rootlesskit --state-dir=/run/user/1000/dockerd-rootless --net=slirp4netns --mtu=65520 --slirp4netns-sandbox=auto --slirp4netns-seccomp=auto --disable-host-loopback --port-driver=builtin --copy-up=/etc --copy-up=/run --propagation=rslave /usr/bin/dockerd-rootless.sh
jerome     37978   37967  0 13:51 ?        00:00:00 /proc/self/exe --state-dir=/run/user/1000/dockerd-rootless --net=slirp4netns --mtu=65520 --slirp4netns-sandbox=auto --slirp4netns-seccomp=auto --disable-host-loopback --port-driver=builtin --copy-up=/etc --copy-up=/run --propagation=rslave /usr/bin/dockerd-rootless.sh
jerome     37998   37967  0 13:51 ?        00:00:00 slirp4netns --mtu 65520 -r 3 --disable-host-loopback --enable-sandbox --enable-seccomp 37978 tap0
lsof -i :2283
COMMAND     PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
rootlessk 37967 jerome   13u  IPv4 210791      0t0  TCP *:2283 (LISTEN)
rootlessk 37967 jerome   16u  IPv6 213520      0t0  TCP *:2283 (LISTEN)
jerome@mac-mini-ubuntu:~/immich-app$ ps -edf |grep 37967
jerome     37967   11719  0 13:51 ?        00:00:00 rootlesskit --state-dir=/run/user/1000/dockerd-rootless --net=slirp4netns --mtu=65520 --slirp4netns-sandbox=auto --slirp4netns-seccomp=auto --disable-host-loopback --port-driver=builtin --copy-up=/etc --copy-up=/run --propagation=rslave /usr/bin/dockerd-rootless.sh
jerome     37978   37967  0 13:51 ?        00:00:00 /proc/self/exe --state-dir=/run/user/1000/dockerd-rootless --net=slirp4netns --mtu=65520 --slirp4netns-sandbox=auto --slirp4netns-seccomp=auto --disable-host-loopback --port-driver=builtin --copy-up=/etc --copy-up=/run --propagation=rslave /usr/bin/dockerd-rootless.sh
jerome     37998   37967  0 13:51 ?        00:00:00 slirp4netns --mtu 65520 -r 3 --disable-host-loopback --enable-sandbox --enable-seccomp 37978 tap0
2 Replies
Immich
Immich•4mo ago
:wave: Hey @jeromecodeium, Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA Checklist I have... 1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time). 2. :blue_square: read applicable release notes. 3. :blue_square: reviewed the FAQs for known issues. 4. :blue_square: reviewed Github for known issues. 5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy). 6. :blue_square: uploaded the relevant information (see below). 7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable (an item can be marked as "complete" by reacting with the appropriate number) Information In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider: - Your docker-compose.yml and .env files. - Logs from all the containers and their status (see above). - All the troubleshooting steps you've tried so far. - Any recent changes you've made to Immich or your system. - Details about your system (both software/OS and hardware). - Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h). - The version of the Immich server, mobile app, and other relevant pieces. - Any other information that you think might be relevant. Please paste files and logs with proper code formatting, and especially avoid blurry screenshots. Without the right information we can't work out what the problem is. Help us help you ;) If this ticket can be closed you can use the /close command, and re-open it later if needed.
Zeus
Zeus•4mo ago
Your host is Mac? Please post logs for all containers

Did you find this page helpful?