I
Immich•3y ago
c0mputerking

Internal server error (500 - Internal Server Error)

Get this error when i click on Explore
24 Replies
Alex Tran
Alex Tran•3y ago
Have you run the CLIP embedding job yet?
c0mputerking
c0mputerkingOP•3y ago
No
Alex Tran
Alex Tran•3y ago
Can you run that first then try to access the explore page again? And which version of the server are you on?
c0mputerking
c0mputerkingOP•3y ago
v1.51.1
Alex Tran
Alex Tran•3y ago
That is the right version, I believe once you finished running the CLIP embedding job, it should solve the problem
c0mputerking
c0mputerkingOP•3y ago
i have run the ENCODE CLIP seems to be stuck on waiting ?? all jobs are in a waiting status .. i have only loaded 2 photos so fare
Alex Tran
Alex Tran•3y ago
Please provide the log of the server and microservice
c0mputerking
c0mputerkingOP•3y ago
not quite sure how to do that sorry I actually did not expect such amazing support Ok think i have figured out the docker logs thing
c0mputerking
c0mputerkingOP•3y ago
[Nest] 1 - 03/22/2023, 7:02:01 PM ERROR [ExceptionsHandler] Request failed with HTTP code 404 | Server said: Not Found ObjectNotFound: Request failed with HTTP code 404 | Server said: Not Found at ObjectNotFound.TypesenseError [as constructor] (/usr/src/app/node_modules/typesense/lib/Typesense/Errors/TypesenseError.js:23:28) at new ObjectNotFound (/usr/src/app/node_modules/typesense/lib/Typesense/Errors/ObjectNotFound.js:25:42) at ApiCall.customErrorForResponse (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:338:21) at /usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:199:98 at step (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:33:23) at Object.next (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:14:53) at step (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:18:139) at Object.next (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:14:53) at fulfilled (/usr/src/app/node_modules/typesense/lib/Typesense/ApiCall.js:5:58) at runMicrotasks (<anonymous>)
c0mputerking
c0mputerkingOP•3y ago
[Nest] 1 - 03/22/2023, 6:38:06 PM ERROR [SmartInfoService] Unable run clip encoding pipeline: 74cb01ba-34ff-4412-92a5-585a32028cd8 Error: socket hang up at connResetException (node:internal/errors:692:14) at Socket.socketOnEnd (node:_http_client:478:23) at Socket.emit (node:events:539:35) at endReadableNT (node:internal/streams/readable:1345:12) at processTicksAndRejections (node:internal/process/task_queues:83:21) [Nest] 1 - 03/22/2023, 6:58:44 PM ERROR [SmartInfoService] Unable run clip encoding pipeline: 74cb01ba-34ff-4412-92a5-585a32028cd8 Error: socket hang up at connResetException (node:internal/errors:692:14) at Socket.socketOnEnd (node:_http_client:478:23) at Socket.emit (node:events:539:35) at endReadableNT (node:internal/streams/readable:1345:12) at processTicksAndRejections (node:internal/process/task_queues:83:21) migrating-time: 64.328ms
Alex Tran
Alex Tran•3y ago
Do you have machine learning up?
c0mputerking
c0mputerkingOP•3y ago
not to sure how do i check?
Alex Tran
Alex Tran•3y ago
docker logs immich_machine_learning or docker logs immich_machinelearning
Alex Tran
Alex Tran•3y ago
The first time you ran, it was downloading the models, it should be working now, can you check the job page again to see if they have finished running?
c0mputerking
c0mputerkingOP•3y ago
Darn they still all say waiting
No description
Alex Tran
Alex Tran•3y ago
Does it help with solving the original issue?
c0mputerking
c0mputerkingOP•3y ago
Nope sorry
Alex Tran
Alex Tran•3y ago
And you only have 2 photos uploaded? There is 0 waiting
c0mputerking
c0mputerkingOP•3y ago
only one now i actually deleted one
Alex Tran
Alex Tran•3y ago
Maybe upload a coupe more, maybe 10 to try
c0mputerking
c0mputerkingOP•3y ago
OK I will try uploading more soon ... but for now i gotta go for bit will be back later THANK YOU this support is unbelievable and so is IMMICH looks like you got a new client 🙂 all i can say is WOW and Thanks again in advance
Alex Tran
Alex Tran•3y ago
No problem my friend
jrasm91
jrasm91•3y ago
Might be worth restarting the server container

Did you find this page helpful?