Machine learning request to "http://immich-machine-learning:3003" failed: fetch failed
I was unable to write the post into message, see attached file. Sorry, I have never written a Discord post before.
9 Replies
:wave: Hey @Prorok Rak,
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.Please try without all the custom network stuff
At first, there was no custom stuff, except for network. Without network section, I was not even able to start Immich after updating to new version. On each run, the containers received new IP address and it was blocked by firewall.
See the attachment what logs said at the time. You can see it was no different.
Most importantly, there was no port exposed on immich-machine-learning service, and no change in Admim > Settings.
It's not that I don't believe you, it's to have a good starting point for further troubleshooting
Sure, but it seems that the network section is a must on my system. It should make sure that the IP address of Immich container does not change on each restart. See the attchached screenshots to see the network settings for immich containers and firewall settings for the given subnet.
I don't see how any of this could cause the error in face detection.
It's fine for the IP to change, that's what DNS is for
Also, it seems that the face detection does not fail completely. As this excerpt from logs shows, there is some successfull detections.
If it's sporadic then it's probably your system getting overloaded
Hm, it might be after all. I went back to standard docker-compose.yml. No custom stuff. Even then, the error occured. So I opened system resources. When the error occured, there was increase in CPU utilization.
