immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-25 03:12:21 +03:00
Code Issues 783 Packages Projects Releases 12 Wiki Activity

Logs flooding with port errors, machine learning searches throw connection errors in logs #3247

New Issue
Closed
opened 2026-02-05 08:06:29 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 08:06:29 +03:00
Owner
Copy Link

Originally created by @bot-nuunuu on GitHub (May 24, 2024).

The bug

I am currently on v1.105.1 on unraid and was seeing the following log flooding the docker logs:

Error: "'3003'" is not a valid port number.

I was also seeing ERCONNREFUSED every time i tried to search with Machine Learning set to on.

I found the issue in /etc/s6-overlay/s6-rc.d/svc-machine-learning/run where the port appears to be surrounded by both single and double quotes, which appears to match the error message. I've circumvented this by adding MACHINE_LEARNING_HOST and MACHINE_LEARNING_PORT container variables to circumvent the default values being set, but I thought I'd leave a quick heads up in case this is an issue outside of just my machine or if this is something related to a recent change.

The OS that Immich Server is running on

Unraid 6.12.10

Version of Immich Server

v1.105.1

Version of Immich Mobile App

n/a

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

n/a

Your .env content

n/a

Reproduction steps

1. start server using defaults for machine learning server
2. errors start appearing

Relevant log output

Error: "'3003'" is not a valid port number.

Additional information

Explicitly setting MACHINE_LEARNING_HOST to 127.0.0.1 and MACHINE_LEARNING_PORT to 3003 in the container variables fixed the issue for me by circumventing the defaults.

Originally created by @bot-nuunuu on GitHub (May 24, 2024). ### The bug I am currently on v1.105.1 on unraid and was seeing the following log flooding the docker logs: Error: "'3003'" is not a valid port number. I was also seeing ERCONNREFUSED every time i tried to search with Machine Learning set to on. I found the issue in /etc/s6-overlay/s6-rc.d/svc-machine-learning/run where the port appears to be surrounded by both single and double quotes, which appears to match the error message. I've circumvented this by adding MACHINE_LEARNING_HOST and MACHINE_LEARNING_PORT container variables to circumvent the default values being set, but I thought I'd leave a quick heads up in case this is an issue outside of just my machine or if this is something related to a recent change. ### The OS that Immich Server is running on Unraid 6.12.10 ### Version of Immich Server v1.105.1 ### Version of Immich Mobile App n/a ### Platform with the issue - [X] Server - [ ] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML n/a ``` ### Your .env content ```Shell n/a ``` ### Reproduction steps ```bash 1. start server using defaults for machine learning server 2. errors start appearing ``` ### Relevant log output ```shell Error: "'3003'" is not a valid port number. ``` ### Additional information Explicitly setting MACHINE_LEARNING_HOST to 127.0.0.1 and MACHINE_LEARNING_PORT to 3003 in the container variables fixed the issue for me by circumventing the defaults.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 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#3247
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?