I
Immich•3mo ago
NoMachine

Help trying to setup remote machine learning - fetch fail on remote host

I'm trying to setup RML on another system, everything looks fine, but the server is unable to connect to the remote ML for some reason. any tip would be appretiated. these are the logs from the server
[Nest] 7  - 02/05/2025, 1:14:03 PM    WARN [Microservices:MachineLearningRepository] Machine learning request to "http://192.168.0.227:3003" failed: fetch failed
[Nest] 7  - 02/05/2025, 1:14:03 PM    WARN [Microservices:MachineLearningRepository] Machine learning request to "http://192.168.0.227:3003" failed: fetch failed
[Nest] 7  - 02/05/2025, 1:14:03 PM    WARN [Microservices:MachineLearningRepository] Machine learning request to "http://192.168.0.227:3003" failed: fetch failed
[Nest] 7  - 02/05/2025, 1:14:03 PM    WARN [Microservices:MachineLearningRepository] Machine learning request to "http://192.168.0.227:3003" failed: fetch failed
I logged into the server console to test if it can reach the server and port 
root@4c5bebf86a06:/usr/src/app# nmap 192.168.0.227 -p 3003
Starting Nmap 7.93 ( https://nmap.org ) at 2025-02-05 13:28 UTC
Nmap scan report for dragonborn (192.168.0.227)
Host is up (0.00048s latency).

PORT     STATE SERVICE
3003/tcp open  cgms
root@4c5bebf86a06:/usr/src/app# nmap 192.168.0.227 -p 3003
Starting Nmap 7.93 ( https://nmap.org ) at 2025-02-05 13:28 UTC
Nmap scan report for dragonborn (192.168.0.227)
Host is up (0.00048s latency).

PORT     STATE SERVICE
3003/tcp open  cgms
and these are the logs from the remote instance 
[02/05/25 12:44:26] INFO     Starting gunicorn 23.0.0                           
[02/05/25 12:44:26] INFO     Listening at: http://[::]:3003 (9)                 
[02/05/25 12:44:26] INFO     Using worker: app.config.CustomUvicornWorker       
[02/05/25 12:44:26] INFO     Booting worker with pid: 10                        
[02/05/25 12:44:29] INFO     Started server process [10]                        
[02/05/25 12:44:29] INFO     Waiting for application startup.                   
[02/05/25 12:44:29] INFO     Created in-memory cache with unloading after 300s  
                             of inactivity.                                     
[02/05/25 12:44:29] INFO     Initialized request thread pool with 12 threads.   
[02/05/25 12:44:29] INFO     Application startup complete.
[02/05/25 12:44:26] INFO     Starting gunicorn 23.0.0                           
[02/05/25 12:44:26] INFO     Listening at: http://[::]:3003 (9)                 
[02/05/25 12:44:26] INFO     Using worker: app.config.CustomUvicornWorker       
[02/05/25 12:44:26] INFO     Booting worker with pid: 10                        
[02/05/25 12:44:29] INFO     Started server process [10]                        
[02/05/25 12:44:29] INFO     Waiting for application startup.                   
[02/05/25 12:44:29] INFO     Created in-memory cache with unloading after 300s  
                             of inactivity.                                     
[02/05/25 12:44:29] INFO     Initialized request thread pool with 12 threads.   
[02/05/25 12:44:29] INFO     Application startup complete.
7 Replies
Immich
Immich•3mo ago
:wave: Hey @NoMachine, 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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: read applicable release notes. 3. :ballot_box_with_check: reviewed the FAQs for known issues. 4. :ballot_box_with_check: reviewed Github for known issues. 5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy). 6. :ballot_box_with_check: uploaded the relevant information (see below). 7. :ballot_box_with_check: 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. Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Mraedis
Mraedis•3mo ago
A little more info on your hosts would be nice, both immich and remote
NoMachine
NoMachineOP•3mo ago
sure, what kind of info you think would be useful? both are running ubuntu server lts, in docker using default proposed docker composer file from the docs
Mraedis
Mraedis•3mo ago
Exactly that 😛
Tempest
Tempest•3mo ago
Is there any firewall on the remote machine? I'm assuming server can ping the remote IP?
NoMachine
NoMachineOP•3mo ago
turns out I'm stupid and had the wrong docker IP mapped 🤦 it's working perfectly now
Immich
Immich•3mo ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?