When following the installation directions, it deploys and launches the site, but only a few seconds later, the site crashes, leaving it to time out load until I restart the container:
Listening on port 7575 url: http://45a6db1c463b:7575Error: socket hang up at connResetException (node:internal/errors:720:14) at Socket.socketOnEnd (node:_http_client:519:23) at Socket.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1376:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { code: 'ECONNRESET'}
Listening on port 7575 url: http://45a6db1c463b:7575Error: socket hang up at connResetException (node:internal/errors:720:14) at Socket.socketOnEnd (node:_http_client:519:23) at Socket.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1376:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { code: 'ECONNRESET'}
Now, this is running on ARM, so I tried replacing the image with the marked arm64 version, and it's now even more different:
Error [TRPCClientError]: Invalid `prisma.user.count()` invocation:Prisma Client could not locate the Query Engine for runtime "linux-arm64-openssl-3.0.x".This happened because Prisma Client was generated for "debian-openssl-1.1.x", but the actual deployment required "linux-arm64-openssl-3.0.x".Add "linux-arm64-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it:generator client { provider = "prisma-client-js" binaryTargets = ["native", "linux-musl-openssl-3.0.x", "linux-musl-arm64-openssl-3.0.x", "debian-openssl-3.0.x", "linux-arm64-openssl-3.0.x"]}The following locations have been searched: /app/node_modules/.prisma/client /app/node_modules/@prisma/client /home/runner/work/homarr/homarr/node_modules/@prisma/client /tmp/prisma-engines /app/prisma at TRPCClientError.from (file:///app/.next/server/src/middleware.js:1647:20) at <unknown> (file:///app/.next/server/src/middleware.js:2261:60) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Error [TRPCClientError]: Invalid `prisma.user.count()` invocation:Prisma Client could not locate the Query Engine for runtime "linux-arm64-openssl-3.0.x".This happened because Prisma Client was generated for "debian-openssl-1.1.x", but the actual deployment required "linux-arm64-openssl-3.0.x".Add "linux-arm64-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it:generator client { provider = "prisma-client-js" binaryTargets = ["native", "linux-musl-openssl-3.0.x", "linux-musl-arm64-openssl-3.0.x", "debian-openssl-3.0.x", "linux-arm64-openssl-3.0.x"]}The following locations have been searched: /app/node_modules/.prisma/client /app/node_modules/@prisma/client /home/runner/work/homarr/homarr/node_modules/@prisma/client /tmp/prisma-engines /app/prisma at TRPCClientError.from (file:///app/.next/server/src/middleware.js:1647:20) at <unknown> (file:///app/.next/server/src/middleware.js:2261:60) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
I'm kind of at a loss on what I'm able to do. The only issue I found was this: https://github.com/ajnart/homarr/issues/1283 I did comment on it, but I thought I'd shoot my shot here. Any help would be appreciated. Thank you!
Environment NodeJS Version 0.13.2 Describe the problem app folder dump from docker,run with:node server.js 0.12.3 run good but 0.13.2:Internal Server Error synology DS920+ DSM7.2 node 18.15.0 Logs ...
Solution
We did merge the Drizzle PR... Can you delete the database and re-try?
A sleek, modern dashboard that puts all of your apps and services at your fingertips. Control everything in one convenient location. Seamlessly integrates with the apps you've added, providing you with valuable information.