immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-05 00:30:57 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

[BUG] 500 getaddrinfo ENOTFOUND immich-server #765

New Issue
Closed
opened 2026-02-04 22:21:51 +03:00 by OVERLORD · 31 comments
OVERLORD commented 2026-02-04 22:21:51 +03:00
Owner
Copy Link

Originally created by @MozPri on GitHub (Mar 23, 2023).

The bug

Can't access Immich web page since version v1.51.0.
I get 500 getaddrinfo ENOTFOUND immich-server error.

_immich_server_logs.txt

The OS that Immich Server is running on

Debian 11

Version of Immich Server

v1.51.2

Version of Immich Mobile App

v1.51.0

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

Latest from the docs

Your .env content

Latest from the docs

Reproduction steps

1. Install Immich with Portainer or docker-compose
2. Go to the Immich web page

Additional information

No response

Originally created by @MozPri on GitHub (Mar 23, 2023). ### The bug Can't access Immich web page since version v1.51.0. I get 500 getaddrinfo ENOTFOUND immich-server error. [_immich_server_logs.txt](https://github.com/immich-app/immich/files/11049569/_immich_server_logs.txt) ### The OS that Immich Server is running on Debian 11 ### Version of Immich Server v1.51.2 ### Version of Immich Mobile App v1.51.0 ### Platform with the issue - [X] Server - [X] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML Latest from the docs ``` ### Your .env content ```Shell Latest from the docs ``` ### Reproduction steps ```bash 1. Install Immich with Portainer or docker-compose 2. Go to the Immich web page ``` ### Additional information _No response_
OVERLORD commented 2026-02-04 22:21:56 +03:00
Author
Owner
Copy Link

@bo0tzz commented on GitHub (Mar 23, 2023):

Is the typesense container running? The server can't reach it.

@bo0tzz commented on GitHub (Mar 23, 2023): Is the typesense container running? The server can't reach it.
OVERLORD commented 2026-02-04 22:22:01 +03:00
Author
Owner
Copy Link

@MozPri commented on GitHub (Mar 23, 2023):

It's running if I add restart: always. But it's not running without it.

Edit: Actually it's not running. Just restarting...

@MozPri commented on GitHub (Mar 23, 2023): It's running if I add `restart: always`. But it's not running without it. Edit: Actually it's not running. Just restarting...
OVERLORD commented 2026-02-04 22:22:05 +03:00
Author
Owner
Copy Link

@bo0tzz commented on GitHub (Mar 23, 2023):

You'll need to enable logging on the typesense container to figure out why it's having trouble starting. Either way this is not a problem in Immich, so I'll close this issue.

@bo0tzz commented on GitHub (Mar 23, 2023): You'll need to enable logging on the typesense container to figure out why it's having trouble starting. Either way this is not a problem in Immich, so I'll close this issue.
OVERLORD commented 2026-02-04 22:22:07 +03:00
Author
Owner
Copy Link

@tinju87 commented on GitHub (Mar 23, 2023):

Same problem with docker-compose running on portainer.
"Failure Unable to retrieve container logs" for typesense container

@tinju87 commented on GitHub (Mar 23, 2023): Same problem with docker-compose running on portainer. "Failure Unable to retrieve container logs" for typesense container
OVERLORD commented 2026-02-04 22:22:08 +03:00
Author
Owner
Copy Link

@tinju87 commented on GitHub (Mar 23, 2023):

TYPESENSE_API_KEY is missing in the env file and needed by typesense container.
Adding TYPESENSE_API_KEY to the env with whatever value worked for me.

Edit: Please also mention how to update to latest version using portainer in the docs.

@tinju87 commented on GitHub (Mar 23, 2023): TYPESENSE_API_KEY is missing in the env file and needed by typesense container. Adding TYPESENSE_API_KEY to the env with whatever value worked for me. Edit: Please also mention how to update to latest version using portainer in the docs.
OVERLORD commented 2026-02-04 22:22:12 +03:00
Author
Owner
Copy Link

@MozPri commented on GitHub (Mar 23, 2023):

It seems that typesense requires a CPU with AVX support, which I don't have...
https://github.com/typesense/typesense/issues/423#issuecomment-955146700

Maybe this should be mentioned in sys requirements.

@MozPri commented on GitHub (Mar 23, 2023): It seems that typesense requires a CPU with AVX support, which I don't have... https://github.com/typesense/typesense/issues/423#issuecomment-955146700 Maybe this should be mentioned in sys requirements.
OVERLORD commented 2026-02-04 22:22:16 +03:00
Author
Owner
Copy Link

@bo0tzz commented on GitHub (Mar 23, 2023):

Good find, I think we weren't aware of that! We are planning to make typesense an optional component in a future release.

@bo0tzz commented on GitHub (Mar 23, 2023): Good find, I think we weren't aware of that! We are planning to make typesense an optional component in a future release.
OVERLORD commented 2026-02-04 22:22:18 +03:00
Author
Owner
Copy Link

@Peda1996 commented on GitHub (Mar 25, 2023):

I have the same problem, after updating to the newest version, my immich instance (proxmox instance: debian 5.10.162-1) won't boot up.

getaddrinfo ENOTFOUND immich-server
Where can I find log files, that I can attach to that issue? Im using a dell wyse 5070 thin client as my system.

edit: I'm having the same issues with the typesense_api_key? How can I fix this?

@Peda1996 commented on GitHub (Mar 25, 2023): I have the same problem, after updating to the newest version, my immich instance (proxmox instance: debian 5.10.162-1) won't boot up. ` getaddrinfo ENOTFOUND immich-server ` Where can I find log files, that I can attach to that issue? Im using a dell wyse 5070 thin client as my system. edit: I'm having the same issues with the typesense_api_key? How can I fix this?
OVERLORD commented 2026-02-04 22:22:21 +03:00
Author
Owner
Copy Link

@MozPri commented on GitHub (Mar 25, 2023):

@Peda1996 Try disabling machine learning and typesense.
Add this to env variables:

IMMICH_MACHINE_LEARNING_URL=false
TYPESENSE_ENABLED=false

Logs:
https://documentation.immich.app/docs/guides/docker-help#logs

@MozPri commented on GitHub (Mar 25, 2023): @Peda1996 Try disabling machine learning and typesense. Add this to env variables: ``` IMMICH_MACHINE_LEARNING_URL=false TYPESENSE_ENABLED=false ``` Logs: https://documentation.immich.app/docs/guides/docker-help#logs
OVERLORD commented 2026-02-04 22:22:25 +03:00
Author
Owner
Copy Link

@florihupf commented on GitHub (Mar 26, 2023):

Running into the same thing.

Should this be re-opened?

@florihupf commented on GitHub (Mar 26, 2023): Running into the same thing. Should this be re-opened?
OVERLORD commented 2026-02-04 22:22:28 +03:00
Author
Owner
Copy Link

@florihupf commented on GitHub (Mar 26, 2023):

Ah, never mind. Didn't realize I need to update .env.

@florihupf commented on GitHub (Mar 26, 2023): Ah, never mind. Didn't realize I need to update .env.
OVERLORD commented 2026-02-04 22:22:30 +03:00
Author
Owner
Copy Link

@florihupf commented on GitHub (Mar 26, 2023):

Dang it, I got it all working and that search is SO SUPER AWESOME!

TYTYTYTY!

@florihupf commented on GitHub (Mar 26, 2023): Dang it, I got it all working and that search is SO SUPER AWESOME! TYTYTYTY!
OVERLORD commented 2026-02-04 22:22:31 +03:00
Author
Owner
Copy Link

@Peda1996 commented on GitHub (Mar 26, 2023):

Oh, sorry forgot to mention that I already fixed it with the help of
discord. Fixed it as followed:

  1. add these to .env
    TYPESENSE_API_KEY=some-random-text

  2. exchange your docker compose for the newest version

Now just update like you would regularly update the service:

  1. docker compose pull
  2. docker compose up -d

Florian Sauer @.***> schrieb am So., 26. März 2023,
18:05:

Dang it, I got it all working and that search is SO SUPER AWESOME!

TYTYTYTY!

—
Reply to this email directly, view it on GitHub
https://github.com/immich-app/immich/issues/2055#issuecomment-1484143011,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANU6NLIBTOTWIAXHM3UACLW6BZL7ANCNFSM6AAAAAAWE7OKFU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Peda1996 commented on GitHub (Mar 26, 2023): Oh, sorry forgot to mention that I already fixed it with the help of discord. Fixed it as followed: 1. add these to .env TYPESENSE_API_KEY=some-random-text 2. exchange your docker compose for the newest version Now just update like you would regularly update the service: 1. docker compose pull 2. docker compose up -d Florian Sauer ***@***.***> schrieb am So., 26. März 2023, 18:05: > Dang it, I got it all working and that search is SO SUPER AWESOME! > > TYTYTYTY! > > — > Reply to this email directly, view it on GitHub > <https://github.com/immich-app/immich/issues/2055#issuecomment-1484143011>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AANU6NLIBTOTWIAXHM3UACLW6BZL7ANCNFSM6AAAAAAWE7OKFU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
OVERLORD commented 2026-02-04 22:22:35 +03:00
Author
Owner
Copy Link

@Snuupy commented on GitHub (Apr 23, 2023):

@bertmelis do you think we can get a non-avx image working here?

@Snuupy commented on GitHub (Apr 23, 2023): @bertmelis do you think we can get a non-avx image working here?
OVERLORD commented 2026-02-04 22:22:41 +03:00
Author
Owner
Copy Link

@bertmelis commented on GitHub (Apr 23, 2023):

I don't know. I guess I can start a build container: https://github.com/typesense/typesense#build-from-source and see what happens.

Edit: after some minor changes to their Docker build script, it's building. I have no clue about the outcome or the time it takes.
(changes: replace docker by podman and satisfy SELinux, you might not have to do this)

@bertmelis commented on GitHub (Apr 23, 2023): I don't know. I guess I can start a build container: https://github.com/typesense/typesense#build-from-source and see what happens. Edit: after some minor changes to their Docker build script, it's building. I have no clue about the outcome or the time it takes. (changes: replace docker by podman and satisfy SELinux, you might not have to do this)
OVERLORD commented 2026-02-04 22:22:44 +03:00
Author
Owner
Copy Link

@bertmelis commented on GitHub (Apr 23, 2023):

So. I just built Typesense from source, using the script in the typesense repo and pointed the compose file to the locally generated image.

On my J4105 it took a less then 4 hours. Not a big deal to do it yourself. It also doesn't clutter your system with all kind of dependencies because the build process is entirely contained in build containers.

I probably won't publish an image because it actually is just too easy to create one yourself. And then it is built for your cpu.

I'm happy to write the instructions if you need help.

@bertmelis commented on GitHub (Apr 23, 2023): So. I just built Typesense from source, using the script in the typesense repo and pointed the compose file to the locally generated image. On my J4105 it took a less then 4 hours. Not a big deal to do it yourself. It also doesn't clutter your system with all kind of dependencies because the build process is entirely contained in build containers. I probably won't publish an image because it actually is just too easy to create one yourself. And then it is built for **your** cpu. I'm happy to write the instructions if you need help.
OVERLORD commented 2026-02-04 22:22:51 +03:00
Author
Owner
Copy Link

@Snuupy commented on GitHub (Apr 23, 2023):

I'll give it a try! Thanks!

@Snuupy commented on GitHub (Apr 23, 2023): I'll give it a try! Thanks!
OVERLORD commented 2026-02-04 22:22:55 +03:00
Author
Owner
Copy Link

@Snuupy commented on GitHub (Apr 23, 2023):

How do you get docker to reference the locally built typesense image in the compose file?

My typesense build worked after running the command several times due to some checksums not working. Eventually it did build though (not sure how long it took, walked away and got some food, when I came back build was done). It was tagged by default as typesense/typesense:nightly, which I re-tagged as typesense (in attempts of trying to make it not pull latest from dockerhub).

However, when I run docker compose pull, docker will complain that the repo typesense does not exist (which rightfully so, it does not on dockerhub). How do I get pull to skip typesense and provide a local image to be used instead? up -d works in the meantime.

@Snuupy commented on GitHub (Apr 23, 2023): How do you get docker to reference the locally built typesense image in the compose file? My typesense build worked after running the command several times due to some checksums not working. Eventually it did build though (not sure how long it took, walked away and got some food, when I came back build was done). It was tagged by default as `typesense/typesense:nightly`, which I re-tagged as `typesense` (in attempts of trying to make it not pull latest from dockerhub). However, when I run `docker compose pull`, docker will complain that the repo `typesense` does not exist (which rightfully so, it does not on dockerhub). How do I get `pull` to skip typesense and provide a local image to be used instead? `up -d` works in the meantime.
OVERLORD commented 2026-02-04 22:23:01 +03:00
Author
Owner
Copy Link

@bertmelis commented on GitHub (Apr 23, 2023):

This should go in your composefile:

image: localhost/typesense/typesense:nightly

If you omit the localhost, it searches in the (online) registries as found in your configuration files.

@bertmelis commented on GitHub (Apr 23, 2023): This should go in your composefile: image: localhost/typesense/typesense:nightly If you omit the localhost, it searches in the (online) registries as found in your configuration files.
OVERLORD commented 2026-02-04 22:23:07 +03:00
Author
Owner
Copy Link

@Snuupy commented on GitHub (Apr 23, 2023):

If I paste that in, I get: Error response from daemon: error unmarshalling content: invalid character '<' looking for beginning of value

  typesense:
    container_name: immich_typesense
    # image: typesense/typesense:0.24.0
    image: localhost/typesense/typesense:nightly
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
    # logging:
    #   driver: none
    volumes:
      - tsdata:/data
    restart: always
@Snuupy commented on GitHub (Apr 23, 2023): If I paste that in, I get: `Error response from daemon: error unmarshalling content: invalid character '<' looking for beginning of value` ``` typesense: container_name: immich_typesense # image: typesense/typesense:0.24.0 image: localhost/typesense/typesense:nightly environment: - TYPESENSE_API_KEY=${TYPESENSE_API_KEY} - TYPESENSE_DATA_DIR=/data # logging: # driver: none volumes: - tsdata:/data restart: always ```
OVERLORD commented 2026-02-04 22:23:10 +03:00
Author
Owner
Copy Link

@bertmelis commented on GitHub (Apr 23, 2023):

Sorry, I'm using Podman, not Docker. I'm not familiar with your error.

Can you run the image as-is, outside of the Immich stack?

@bertmelis commented on GitHub (Apr 23, 2023): Sorry, I'm using Podman, not Docker. I'm not familiar with your error. Can you run the image as-is, outside of the Immich stack?
OVERLORD commented 2026-02-04 22:23:12 +03:00
Author
Owner
Copy Link

@Snuupy commented on GitHub (Apr 23, 2023):

Via docker run? I don't see why that wouldn't work. It's when I pull that it tries to fetch an image remotely but I want it to use the local one instead.

@Snuupy commented on GitHub (Apr 23, 2023): Via docker run? I don't see why that wouldn't work. It's when I `pull` that it tries to fetch an image remotely but I want it to use the local one instead.
OVERLORD commented 2026-02-04 22:23:17 +03:00
Author
Owner
Copy Link

@bertmelis commented on GitHub (Apr 23, 2023):

Some googling suggests you just shouldn't pull. When the stack is started, docker will find the local image.

https://github.com/docker/compose/issues/3660

@bertmelis commented on GitHub (Apr 23, 2023): Some googling suggests you just shouldn't pull. When the stack is started, docker will find the local image. https://github.com/docker/compose/issues/3660
OVERLORD commented 2026-02-04 22:23:20 +03:00
Author
Owner
Copy Link

@Snuupy commented on GitHub (Apr 23, 2023):

Some googling suggests you just shouldn't pull. When the stack is started, docker will find the local image.

docker/compose#3660

Wait - but I need to pull to update immich

I did the build workaround for now

Edit: pull_policy: never is likely more correct https://github.com/docker/compose/issues/3660#issuecomment-972818887

@Snuupy commented on GitHub (Apr 23, 2023): > Some googling suggests you just shouldn't pull. When the stack is started, docker will find the local image. > > [docker/compose#3660](https://github.com/docker/compose/issues/3660) Wait - but I need to pull to update immich ~~I did the `build` workaround for now~~ Edit: `pull_policy: never` is likely more correct https://github.com/docker/compose/issues/3660#issuecomment-972818887
OVERLORD commented 2026-02-04 22:23:22 +03:00
Author
Owner
Copy Link

@rkononov commented on GitHub (Aug 6, 2023):

I don't know. I guess I can start a build container: https://github.com/typesense/typesense#build-from-source and see what happens.

Edit: after some minor changes to their Docker build script, it's building. I have no clue about the outcome or the time it takes.
(changes: replace docker by podman and satisfy SELinux, you might not have to do this)

Could you please share the changes you introduced?

@rkononov commented on GitHub (Aug 6, 2023): > I don't know. I guess I can start a build container: https://github.com/typesense/typesense#build-from-source and see what happens. > > Edit: after some minor changes to their Docker build script, it's building. I have no clue about the outcome or the time it takes. > (changes: replace docker by podman and satisfy SELinux, you might not have to do this) Could you please share the changes you introduced?
OVERLORD commented 2026-02-04 22:23:25 +03:00
Author
Owner
Copy Link

@bertmelis commented on GitHub (Aug 6, 2023):

I'm using postman on a SELinux-enabled machine.

The two changes:

  • replaced docker command with podman command
  • added :Z flags to volume mounts
@bertmelis commented on GitHub (Aug 6, 2023): I'm using postman on a SELinux-enabled machine. The two changes: - replaced docker command with podman command - added :Z flags to volume mounts
OVERLORD commented 2026-02-04 22:23:30 +03:00
Author
Owner
Copy Link

@55nevets commented on GitHub (Nov 9, 2023):

So. I just built Typesense from source, using the script in the typesense repo and pointed the compose file to the locally generated image.

On my J4105 it took a less then 4 hours. Not a big deal to do it yourself. It also doesn't clutter your system with all kind of dependencies because the build process is entirely contained in build containers.

I probably won't publish an image because it actually is just too easy to create one yourself. And then it is built for your cpu.

I'm happy to write the instructions if you need help.

@bertmelis: I'm interested in compiling typesense for my Intel N5100. Could you provide your build script? Are you still running this non-avx version, and has it been sufficient for a personal immich install?

@55nevets commented on GitHub (Nov 9, 2023): > So. I just built Typesense from source, using the script in the typesense repo and pointed the compose file to the locally generated image. > > On my J4105 it took a less then 4 hours. Not a big deal to do it yourself. It also doesn't clutter your system with all kind of dependencies because the build process is entirely contained in build containers. > > I probably won't publish an image because it actually is just too easy to create one yourself. And then it is built for **your** cpu. > > I'm happy to write the instructions if you need help. @bertmelis: I'm interested in compiling typesense for my Intel N5100. Could you provide your build script? Are you still running this non-avx version, and has it been sufficient for a personal immich install?
OVERLORD commented 2026-02-04 22:23:36 +03:00
Author
Owner
Copy Link

@bertmelis commented on GitHub (Nov 9, 2023):

I'm still running it. For me it is sufficient. It might take a tad longer but it's a background task. It still processes the pictures faster than I shoot them.

I don't know how I built the container but I might find some leftovers on my home server... Stay tuned.

@bertmelis commented on GitHub (Nov 9, 2023): I'm still running it. For me it is sufficient. It might take a tad longer but it's a background task. It still processes the pictures faster than I shoot them. I don't know how I built the container but I might find some leftovers on my home server... Stay tuned.
OVERLORD commented 2026-02-04 22:23:38 +03:00
Author
Owner
Copy Link

@Snuupy commented on GitHub (Nov 10, 2023):

@bertmelis: I'm interested in compiling typesense for my Intel N5100. Could you provide your build script? Are you still running this non-avx version, and has it been sufficient for a personal immich install?

fyi you need to build this version: https://github.com/immich-app/immich/blob/main/docker/docker-compose.yml#L55C4-L55C4

please see: https://github.com/immich-app/immich/discussions/300#discussioncomment-6632119

Just follow these instructions: https://github.com/typesense/typesense/tree/v0.24.1#build-from-source

@Snuupy commented on GitHub (Nov 10, 2023): > @bertmelis: I'm interested in compiling typesense for my Intel N5100. Could you provide your build script? Are you still running this non-avx version, and has it been sufficient for a personal immich install? fyi you need to build this version: https://github.com/immich-app/immich/blob/main/docker/docker-compose.yml#L55C4-L55C4 please see: https://github.com/immich-app/immich/discussions/300#discussioncomment-6632119 Just follow these instructions: https://github.com/typesense/typesense/tree/v0.24.1#build-from-source
OVERLORD commented 2026-02-04 22:23:44 +03:00
Author
Owner
Copy Link

@bertmelis commented on GitHub (Nov 10, 2023):

ah yes. Typesense is on v0.25 but Immich uses v0.24. The instructions to build it yourself are extremely simple: just download/clone the Typesense repo with the correct version and execute the script.

@bertmelis commented on GitHub (Nov 10, 2023): ah yes. Typesense is on v0.25 but Immich uses v0.24. The instructions to build it yourself are extremely simple: just download/clone the Typesense repo with the correct version and execute the script.
OVERLORD commented 2026-02-04 22:23:45 +03:00
Author
Owner
Copy Link

@756yang commented on GitHub (Nov 22, 2023):

After my inspection, the official archive compiled by typesense supports most x64 platforms. Based on the platform instruction set, it requires at least SSE2, SSSE3, SSE4.1 support, and may require SSE3 and SSE4.2 support.

The AVX instruction set is additional and not necessarily required.

@756yang commented on GitHub (Nov 22, 2023): After my inspection, the official archive compiled by typesense supports most x64 platforms. Based on the platform instruction set, it requires at least SSE2, SSSE3, SSE4.1 support, and may require SSE3 and SSE4.2 support. The AVX instruction set is additional and not necessarily required.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:translation
cli
date-time
documentation
external-library
format
good first issue
needs-answer
nice to have
sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#765
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?