June 27, 20251 yr Hi everyone,I'm in the process of setting up Immich self hosting service for photos.Following to the T AlienTech 24 youtube tutorial.All seems to be working ( green running arrow)When I click on the Immich icon, then click WebUI, a window / tab opens and reports: This site can't be reached. IP OFF UNRAID refused to connect.I'm a fairly new noob to Unraid and Docker.I do know that I have (tried) to install a couple of Docker instances and that quasi all times I had the same problem.E.g. with qBittorrentvpn I had the same trouble.From reading and searching I guess this must be a basic config error on my behalf.How can I start to debug this?What does work?I can connect to the consoleHere is a snippet from the log running byAnd also please find the diagnostics attached.For what it's worth I was thinking the ports are not properly aligned, but I'm not sure about that, and I could not change the Docker 8080 port?If you need more information to help me get this working, please let me know!Thanks for helping out!(P.S. I tried to start this topic in the Docker sub-forum, but apparently something went wrong. If you feel like moving it to the Docker sub-forum please do)Node.js v22.16.0api worker exited with code 1libatomic1 libjemalloc2 liblzf1 redis-toolsSuggested packages:ruby-redisThe following NEW packages will be installed:libatomic1 libjemalloc2 liblzf1 redis-server redis-tools0 upgraded, 5 newly installed, 0 to remove and 21 not upgraded.Need to get 1,492 kB of archives.After this operation, 7,608 kB of additional disk space will be used.Get:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 libatomic1 amd64 14.2.0-4ubuntu2~24.04 [10.5 kB]Get:2 http://archive.ubuntu.com/ubuntu noble/universe amd64 libjemalloc2 amd64 5.3.0-2build1 [256 kB]Get:3 http://archive.ubuntu.com/ubuntu noble/universe amd64 liblzf1 amd64 3.6-4 [7,624 B]Get:4 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 redis-tools amd64 5:7.0.15-1ubuntu0.24.04.1 [1,166 kB]Get:5 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 redis-server amd64 5:7.0.15-1ubuntu0.24.04.1 [51.7 kB]Fetched 1,492 kB in 0s (4,344 kB/s)Selecting previously unselected package libatomic1:amd64.(Reading database ... 19371 files and directories currently installed.)Preparing to unpack .../libatomic1_14.2.0-4ubuntu2~24.04_amd64.deb ...Unpacking libatomic1:amd64 (14.2.0-4ubuntu2~24.04) ...Selecting previously unselected package libjemalloc2:amd64.Preparing to unpack .../libjemalloc2_5.3.0-2build1_amd64.deb ...Unpacking libjemalloc2:amd64 (5.3.0-2build1) ...Selecting previously unselected package liblzf1:amd64.Preparing to unpack .../liblzf1_3.6-4_amd64.deb ...Unpacking liblzf1:amd64 (3.6-4) ...Selecting previously unselected package redis-tools.Preparing to unpack .../redis-tools_5%3a7.0.15-1ubuntu0.24.04.1_amd64.deb ...Unpacking redis-tools (5:7.0.15-1ubuntu0.24.04.1) ...Selecting previously unselected package redis-server.Preparing to unpack .../redis-server_5%3a7.0.15-1ubuntu0.24.04.1_amd64.deb ...Unpacking redis-server (5:7.0.15-1ubuntu0.24.04.1) ...Setting up libjemalloc2:amd64 (5.3.0-2build1) ...Setting up liblzf1:amd64 (3.6-4) ...Setting up libatomic1:amd64 (14.2.0-4ubuntu2~24.04) ...Setting up redis-tools (5:7.0.15-1ubuntu0.24.04.1) ...Setting up redis-server (5:7.0.15-1ubuntu0.24.04.1) ...invoke-rc.d: could not determine current runlevelinvoke-rc.d: policy-rc.d denied execution of start.Processing triggers for libc-bin (2.39-0ubuntu8.4) ...[custom-init] No custom files found, skipping...Starting api worker[Nest] 685 - 06/27/2025, 6:56:48 PM LOG [Api:EventRepository] Initialized websocket serverStarting api worker[Nest] 715 - 06/27/2025, 6:56:54 PM LOG [Api:EventRepository] Initialized websocket serverStarting api worker[Nest] 744 - 06/27/2025, 6:56:59 PM LOG [Api:EventRepository] Initialized websocket serverStarting api worker[Nest] 773 - 06/27/2025, 6:57:05 PM LOG [Api:EventRepository] Initialized websocket server/app/immich/server/node_modules/postgres/cjs/src/connection.js:388if (!query || typeof query !== 'object' || !query.reject) throw err^Error: connect ECONNREFUSED 192.168.1.112:5432at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16) {errno: -111,code: 'ECONNREFUSED',syscall: 'connect',address: '192.168.1.112',port: 5432}Node.js v22.16.0api worker exited with code 1Starting api worker[Nest] 802 - 06/27/2025, 6:57:10 PM LOG [Api:EventRepository] Initialized websocket server/app/immich/server/node_modules/postgres/cjs/src/connection.js:388if (!query || typeof query !== 'object' || !query.reject) throw err^Error: connect ECONNREFUSED 192.168.1.112:5432at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16) {errno: -111,code: 'ECONNREFUSED',syscall: 'connect',address: '192.168.1.112',port: 5432}Node.js v22.16.0api worker exited with code 1Starting api worker[Nest] 831 - 06/27/2025, 6:57:15 PM LOG [Api:EventRepository] Initialized websocket server/app/immich/server/node_modules/postgres/cjs/src/connection.js:388if (!query || typeof query !== 'object' || !query.reject) throw err^Error: connect ECONNREFUSED 192.168.1.112:5432at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16) {errno: -111,code: 'ECONNREFUSED',syscall: 'connect',address: '192.168.1.112',port: 5432}tower-diagnostics-20250627-1832.zip Edited June 27, 20251 yr by panini
June 27, 20251 yr Community Expert on unraid there are 2 way to install and setup immich. I have 2 guides written for this.The Compose Method:and the Unriad Template CA Method.https://forums.unraid.net/topic/190531-guide-immich-docker-setup-unraid-caAdditional support can be found here:also the unriad immich docker CA template support thread is located here:https://forums.unraid.net/topic/146106-immich-docker-self-hosted-google-photos-setup Edited June 27, 20251 yr by bmartino1 Data - Typo
June 27, 20251 yr Community Expert 1 hour ago, panini said:Hi everyone,I'm in the process of setting up Immich self hosting service for photos.Following to the T AlienTech 24 youtube tutorial.All seems to be working ( green running arrow)When I click on the Immich icon, then click WebUI, a window / tab opens and reports: This site can't be reached. IP OFF UNRAID refused to connect.I'm a fairly new noob to Unraid and Docker.I do know that I have (tried) to install a couple of Docker instances and that quasi all times I had the same problem.E.g. with qBittorrentvpn I had the same trouble.From reading and searching I guess this must be a basic config error on my behalf.How can I start to debug this?What does work?I can connect to the consoleHere is a snippet from the log running byAnd also please find the diagnostics attached.For what it's worth I was thinking the ports are not properly aligned, but I'm not sure about that, and I could not change the Docker 8080 port?If you need more information to help me get this working, please let me know!Thanks for helping out!(P.S. I tried to start this topic in the Docker sub-forum, but apparently something went wrong. If you feel like moving it to the Docker sub-forum please do)Node.js v22.16.0api worker exited with code 1libatomic1 libjemalloc2 liblzf1 redis-toolsSuggested packages:ruby-redisThe following NEW packages will be installed:libatomic1 libjemalloc2 liblzf1 redis-server redis-tools0 upgraded, 5 newly installed, 0 to remove and 21 not upgraded.Need to get 1,492 kB of archives.After this operation, 7,608 kB of additional disk space will be used.Get:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 libatomic1 amd64 14.2.0-4ubuntu2~24.04 [10.5 kB]Get:2 http://archive.ubuntu.com/ubuntu noble/universe amd64 libjemalloc2 amd64 5.3.0-2build1 [256 kB]Get:3 http://archive.ubuntu.com/ubuntu noble/universe amd64 liblzf1 amd64 3.6-4 [7,624 B]Get:4 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 redis-tools amd64 5:7.0.15-1ubuntu0.24.04.1 [1,166 kB]Get:5 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 redis-server amd64 5:7.0.15-1ubuntu0.24.04.1 [51.7 kB]Fetched 1,492 kB in 0s (4,344 kB/s)Selecting previously unselected package libatomic1:amd64.(Reading database ... 19371 files and directories currently installed.)Preparing to unpack .../libatomic1_14.2.0-4ubuntu2~24.04_amd64.deb ...Unpacking libatomic1:amd64 (14.2.0-4ubuntu2~24.04) ...Selecting previously unselected package libjemalloc2:amd64.Preparing to unpack .../libjemalloc2_5.3.0-2build1_amd64.deb ...Unpacking libjemalloc2:amd64 (5.3.0-2build1) ...Selecting previously unselected package liblzf1:amd64.Preparing to unpack .../liblzf1_3.6-4_amd64.deb ...Unpacking liblzf1:amd64 (3.6-4) ...Selecting previously unselected package redis-tools.Preparing to unpack .../redis-tools_5%3a7.0.15-1ubuntu0.24.04.1_amd64.deb ...Unpacking redis-tools (5:7.0.15-1ubuntu0.24.04.1) ...Selecting previously unselected package redis-server.Preparing to unpack .../redis-server_5%3a7.0.15-1ubuntu0.24.04.1_amd64.deb ...Unpacking redis-server (5:7.0.15-1ubuntu0.24.04.1) ...Setting up libjemalloc2:amd64 (5.3.0-2build1) ...Setting up liblzf1:amd64 (3.6-4) ...Setting up libatomic1:amd64 (14.2.0-4ubuntu2~24.04) ...Setting up redis-tools (5:7.0.15-1ubuntu0.24.04.1) ...Setting up redis-server (5:7.0.15-1ubuntu0.24.04.1) ...invoke-rc.d: could not determine current runlevelinvoke-rc.d: policy-rc.d denied execution of start.Processing triggers for libc-bin (2.39-0ubuntu8.4) ...[custom-init] No custom files found, skipping...Starting api worker[Nest] 685 - 06/27/2025, 6:56:48 PM LOG [Api:EventRepository] Initialized websocket serverStarting api worker[Nest] 715 - 06/27/2025, 6:56:54 PM LOG [Api:EventRepository] Initialized websocket serverStarting api worker[Nest] 744 - 06/27/2025, 6:56:59 PM LOG [Api:EventRepository] Initialized websocket serverStarting api worker[Nest] 773 - 06/27/2025, 6:57:05 PM LOG [Api:EventRepository] Initialized websocket server/app/immich/server/node_modules/postgres/cjs/src/connection.js:388if (!query || typeof query !== 'object' || !query.reject) throw err^Error: connect ECONNREFUSED 192.168.1.112:5432at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16) {errno: -111,code: 'ECONNREFUSED',syscall: 'connect',address: '192.168.1.112',port: 5432}Node.js v22.16.0api worker exited with code 1Starting api worker[Nest] 802 - 06/27/2025, 6:57:10 PM LOG [Api:EventRepository] Initialized websocket server/app/immich/server/node_modules/postgres/cjs/src/connection.js:388if (!query || typeof query !== 'object' || !query.reject) throw err^Error: connect ECONNREFUSED 192.168.1.112:5432at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16) {errno: -111,code: 'ECONNREFUSED',syscall: 'connect',address: '192.168.1.112',port: 5432}Node.js v22.16.0api worker exited with code 1Starting api worker[Nest] 831 - 06/27/2025, 6:57:15 PM LOG [Api:EventRepository] Initialized websocket server/app/immich/server/node_modules/postgres/cjs/src/connection.js:388if (!query || typeof query !== 'object' || !query.reject) throw err^Error: connect ECONNREFUSED 192.168.1.112:5432at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16) {errno: -111,code: 'ECONNREFUSED',syscall: 'connect',address: '192.168.1.112',port: 5432}tower-diagnostics-20250627-1832.zip"Error: connect ECONNREFUSED 192.168.1.112:5432at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16) {errno: -111,code: 'ECONNREFUSED',syscall: 'connect',address: '192.168.1.112',"Usualy point to an issue and a inabilty to communicate to the postgres docker.
June 27, 20251 yr Author Thanks for replying.I'm not sufficiently knowledgeable but:during install / setup Immich docker tests the connection => no issues were revealedI've had this issue with ALL Docker containersFor what it's worth:I did setup a custom network for Docker. Don't remember, Binhex or who has a Youtube tutorial about this.
June 27, 20251 yr Community Expert regardless the immich log is says that its credentials/ hotname, and its abilty to talk to Postgres is the issues. You need to fix the Postgres docker and update immich to connect...If you restored a Postgres backup and changed password(not use the password from the restore), the restore reverted the password to what it was when it was int eh backup.... You need to verify that you are able to connect to Postgres from another system / other software...PGadmin can be used her to assit with that. to make sure you are able to connect to Postgres.Postgress template docker option don't update or change the password. the temple set it once at creation...you have a communication issues between immich and postgress you need to fix it.. Revew the guide to make a guaranteed communication...you may need to delete the postgress appdata and start over...
June 28, 20251 yr Community Expert Please post the docker run for both postgres and immich containers, remove any sensitive info like db passwords if they're not masked
June 28, 20251 yr Author 9 hours ago, MowMdown said:docker run for both postgres and immichThat would be, for Immich:docker run -d --name='immich' --net='bridge' --pids-limit 2048 -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="immich" -e 'DB_HOSTNAME'='192.168.1.112' -e 'DB_USERNAME'='postgres' -e 'DB_PASSWORD'='postgres' -e 'DB_DATABASE_NAME'='immich' -e 'REDIS_HOSTNAME'='localhost' -e 'DB_PORT'='5432' -e 'REDIS_PORT'='6379' -e 'REDIS_PASSWORD'='' -e 'SERVER_HOST'='0.0.0.0' -e 'SERVER_PORT'='8586' -e 'MACHINE_LEARNING_HOST'='0.0.0.0' -e 'MACHINE_LEARNING_PORT'='3003' -e 'MACHINE_LEARNING_WORKERS'='1' -e 'MACHINE_LEARNING_WORKER_TIMEOUT'='120' -e 'DOCKER_MODS'='imagegenius/mods:universal-redis' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8586]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/imagegenius/templates/main/unraid/img/immich.png' -p '8586:8080/tcp' -v '/mnt/user/media/Photos/':'/photos':'rw' -v '/mnt/user/appdata/immich':'/config':'rw' 'ghcr.io/imagegenius/immich'3c76c5aed8f85e6f3d4a0f11cc0c800f67e09bdf411fac7a8808819289980d5cThe command finished successfully!and for PostgreSQL:docker run -d --name='PostgreSQL_Immich' --net='bridge' --pids-limit 2048 -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="PostgreSQL_Immich" -e 'POSTGRES_PASSWORD'='postgres' -e 'POSTGRES_USER'='postgres' -e 'POSTGRES_DB'='immich' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='' -p '5432:5432/tcp' -v '/mnt/user/appdata/PostgreSQL_Immich':'/var/lib/postgresql/data':'rw' 'tensorchord/pgvecto-rs:pg16-v0.3.0'976f4e2969068dd9eb2daf9b8e52ca2667914e8d5d8b416c30b7b6d2114e9985The command finished successfully!I will also try to install PGAdmin
June 28, 20251 yr Author 2 hours ago, panini said:I will also try to install PGAdminIn the mean time I have installed PGAdmin too. Here's some detail of my experience:first of all I tried hard to pay better attention while going through the install process instead of taking for granted that scripts will run fineI chose to install FoxxMD's version since that was the most recent updated versionI then did the chown as below * Then open unraid cli and change ownership for the directory to 5050:5050 with the following command chown -R 5050:5050 /mnt/user/appdata/pgadmin4 Restart the container to continue setup.And, yes, it worked and, yes, I can connect to the WebUIBut now I would greatly appreciate some feedback on how to proceed next.(In the mean time I will try to go through my previous installs of PostgreSQL and Immich, I guess PostgreSQL is the main thing with the focus on passwords etc, I guess after that using PGAdmin I will somehow be capable of checking the PostgreSQL install and when that is ok, Immich)Thanks for helping out!
June 28, 20251 yr Community Expert what does the postgres log look like after you start it up? I can't see anything wrong with your docker runs for either container... Edited June 28, 20251 yr by MowMdown
June 28, 20251 yr Community Expert The only thing I can suggest is making sure postgres is running BEFORE immich starts up
June 28, 20251 yr Author 39 minutes ago, MowMdown said:s 192.168.1.112 really the IP of unraid?My unraid server's name is Tower.erwin@mini-3 ~ % ping tower.local PING tower.local (192.168.1.112): 56 data bytes 64 bytes from 192.168.1.112: icmp_seq=0 ttl=64 time=1.307 ms 64 bytes from 192.168.1.112: icmp_seq=1 ttl=64 time=0.595 ms 64 bytes from 192.168.1.112: icmp_seq=2 ttl=64 time=0.450 ms ^C --- tower.local ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.450/0.784/1.307/0.375 ms erwin@mini-3 ~ % I have't tried starting Immich later than PostgreSQL. Will do that now.I was also wondering with PGAdmin 4 working and being reachable fine, can we now use it to check on PostgreSQL? Or is the plain fact that the install succeeded and is reachable is enough?
June 28, 20251 yr Author I've tried restarting Immich, (while PostgreSQL was already running)No joy, This site can't be reached, ERR_CONNECTION_REFUSED.
June 28, 20251 yr Community Expert It makes no sense why immich cannot connect to postgres... i really don't see whats wrong.what does the postgres logs say? have you tried deleting the postgres appdata, and restarting postgres before starting immich? Edited June 28, 20251 yr by MowMdown
June 28, 20251 yr Author Ok, I think this might help:I'm not familiar at all with PGAdmin, but I have used it yeaaaaaaaaaars ago when I set up several MAMP servers.So, I took a shot at it and tried to enter the user information to add a server in PGAdmin.And apparently that worked.
June 28, 20251 yr Author Can it have something to do with the user permissions in hte appdata folder?I'm wondering because the PGAdmin4 docker specifically requested to change the user permissions..These three ls -la commands were issued before and after the change to the pgadmin4 docker appdata folder Edited June 28, 20251 yr by panini
June 28, 20251 yr Community Expert 3 hours ago, panini said:Can it have something to do with the user permissions in hte appdata folder?I'm wondering because the PGAdmin4 docker specifically requested to change the user permissions..These three ls -la commands were issued before and after the change to the pgadmin4 docker appdata folderits a potential. I would recommend stopping all dockers. Going to tool > docker safe permission. And run that with all dockers stopped this will sett docker safe permission across the appdata folder... cd /mnt/users/appdata chmod 777 -R * chown nobody:users -R *
June 28, 20251 yr Community Expert also you should switch the image to use my postgress immch docker that uses the vecrot chord. Image genious has moved off the pgvetochord Postgres plugin.be sure to use the same password from both and set the same appdta path for your postgress. Immch gave use a docker that will run the pgvetor database comands to fix teh tables that may also be prevenint the lattest imich CA docker form connectiong to postgres.I'd prefer you get pgadmin working and make a backup first..otherwise if you have the data to reuploaded I would recommend starting Postgres over with this Postgres docker.(This would require deleting the appdata folder.)
June 29, 20251 yr Author 20 hours ago, bmartino1 said:Going to tool > docker safe permission.Ok, here we are again ;-)First of all, thanks a ton for helping out!Second, question, remark:I'm trying to take this whole process as a (big) learning curve towards learning unraid, understanding docker containers and networking in unraid context. To illustrate, I had to research what CA is to find out it's of course the abbreviation of Community Applications. Just to illustrate my level of understanding..So what I did next: install Immich_PostgreSQL from ghcr repo. And configured that with the identical (as far as I can tell) settings and (default) passwords.I then went to search for the tool > docker safe permission only not to find it. After doing again searching, I installed the Fix Common Problems plugin, ran the tests as good as possible (no big things revealed though).In the mean time I went into the terminal and ran chmod & chown manually.cd /mnt/users/appdata chmod 777 -R * chown nobody:users -R *Afterwards, I found the Docker Safe new Permissions in Tools, then ran that too, which is processing a lot more than what I did with the chmod & chown command. But then, after all this, I still get the imminent Here's a copy of the immich.log:text error warn system array login.txtToo me it seems that Immich is correctly running?Looking forward what you suggest to get connected to Immich?Also:Yesterday I could connect to PGAdmin and now this does not work anymore either..
June 29, 20251 yr Community Expert I think it might be a good idea if Limetech added an ‘Common Unraid terms’ page to the online documentation and include abbreviations.
June 29, 20251 yr Community Expert 2 hours ago, panini said:Ok, here we are again ;-)First of all, thanks a ton for helping out!Second, question, remark:I'm trying to take this whole process as a (big) learning curve towards learning unraid, understanding docker containers and networking in unraid context. To illustrate, I had to research what CA is to find out it's of course the abbreviation of Community Applications. Just to illustrate my level of understanding..So what I did next: install Immich_PostgreSQL from ghcr repo. And configured that with the identical (as far as I can tell) settings and (default) passwords.I then went to search for the tool > docker safe permission only not to find it. After doing again searching, I installed the Fix Common Problems plugin, ran the tests as good as possible (no big things revealed though).In the mean time I went into the terminal and ran chmod & chown manually.cd /mnt/users/appdata chmod 777 -R * chown nobody:users -R *Afterwards, I found the Docker Safe new Permissions in Tools, then ran that too, which is processing a lot more than what I did with the chmod & chown command.But then, after all this, I still get the imminent Here's a copy of the immich.log:text error warn system array login.txtToo me it seems that Immich is correctly running?Looking forward what you suggest to get connected to Immich?Also:Yesterday I could connect to PGAdmin and now this does not work anymore either..Few things and apologies, I will remember to use a "CA(Community apps)" moving forward so context stays for new users.1 would need a log from immich if its not error that correct.there appears to be some weird port forwaring issue you are experiencing...Per your picture:as the left looks correct... shows that immich is in docker bridge mode and only port 8080 is being doicker bridge NAT passed and port is open.... but unriad also shows port 8586???SO, if you go to your unraid IP 192.168.1.112:8080 do you hit immich?otherwise make sure your webui port settings are correct and the advance togle webui ip:port to access immich is correct...Double check immich settings:I don't know where you got port 8586and if you want to use port 8586 the docker port in network bridge needs to be:
June 29, 20251 yr Community Expert I would highly recommend reading this post I wrote going over docker networks...https://forums.unraid.net/topic/188695-docker-network-issue/#findComment-1541042and reviewing the docker docs and unraid docs.https://docs.docker.com/engine/network/Docker Management | Unraid DocsDocker Management | Unraid DocsDocker is a technology that allows users to provide each application
June 29, 20251 yr Author 12 minutes ago, bmartino1 said:I would highly recommend reading this post I wrote going over docker networks...Will certainly do!In the mean time:navigating to http://192.168.1.112:8080/ also gives me the refused to connectanother question running in my head: when I try to do something with unraid, I mostly follow tutorials, be it youtube or on the forum. That brings me to the fact that I remember that I created two docker custom networks (without really knowing properly what they do). So my question: can they be removed? If yes, how? Otherwise, can they cause havoc / problems?is it logic that PGAdmin does not work anymore? Edited June 29, 20251 yr by panini
June 29, 20251 yr Community Expert Solution I don't realy know how to use pgadmin. I know that it a good alternative to having users run termianl commands. I had issues with working immich postgress and getting pgadmin to connect and make a backup..sorry I can't help wiht pg admin.The bes I can do is sent you to youtube and other guides...https://www.youtube.com/watch?v=21J06XEbLD4-This is because I can console into the database docker and run sql commands.Regarding the another question running in my headyes yo can remove old docker networkings you created.docker network lsdocker netwrok rm <dockername>see docker docs: https://docs.docker.com/reference/cli/docker/network/rm/it will only cause issues if it is in use with another docker.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.