I have set up Immich on Docker (Running on debian on Proxmox)
I have imported my current photos using the import command which looks like it worked.
The issue I am having is that for whatever reason the thumbnails are not working on the browser but are showing on the iOS App
I have attached the log files
thank you
#Thumbnails not showing
1 messages · Page 1 of 1 (latest)
This isn’t a very helpful error, sorry.
@echo compass I think you looked at this recently?
It can't connect to the postgres database, make sure that is running
It must be able to connect to the db if it can list assets?
The error is a postgres timeout, so something there must be having a bad time at least
hmm the postgres container is throwing some errors as well
Can you right click in the browser, click inspect and check the console tab?
try {
const thumbnailPath = this.getThumbnailPath(asset, query.format);
return this.streamFile(thumbnailPath, res, headers);
} catch (e) {
res.header('Cache-Control', 'none');
this.logger.error(`Cannot create read stream for asset ${asset.id}`, 'getAssetThumbnail');
throw new InternalServerErrorException(
`Cannot read thumbnail file for asset ${asset.id} - contact your administrator`,
{ cause: e as Error },
);
}
The server error is coming from this block. The cause is only reported in the response
OAuth Redirect URI: http://192.168.3.5:2283/auth/login api/jobs:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error) 31.c757ae21.js:6 Uncaught (in promise) Zcode: "ERR_BAD_RESPONSE"config: {transitional: {…}, transformRequest: Array(1), transformResponse: Array(1), timeout: 0, adapter: ƒ, …}message: "Request failed with status code 500"name: "AxiosError"request: XMLHttpRequest {onreadystatechange: null, readyState: 4, timeout: 0, withCredentials: false, upload: XMLHttpRequestUpload, …}response: {data: {…}, status: 500, statusText: 'Internal Server Error', headers: {…}, config: {…}, …}[[Prototype]]: Error
that's what it is showing
ram is looking pretty rough, though i don't know if it would cause this issue
Thanks , I will increase the allocated ram and try again
Have the job: finished running?
Yes #twice