Homarr•14mo ago

"ECONNRESET" all the bugs!

Trying to deploy Homarr on Portainer from 6.5.0-asahi-3-1-ARCH 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:7575
Error: 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:7575
Error: 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!

GitHub

Internal Server Error · Issue #1283 · ajnart/homarr

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?

Jump to solution

22 Replies

LeahOP•14mo ago

The next solution I have is trying an older version of Homarr, but I'm sort of new to Docker and it doesn't seem as easy as npm where you just add an @x.x.x haha! Oh and here's my compose yml:

version: '3'
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.     #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:latest
    restart: unless-stopped
    volumes:
      - /mnt/syrah/homarr/config:/app/data/configs
      - /mnt/syrah/homarr/icons:/app/public/icons
    ports:
      - '7575:7575'

version: '3'
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.     #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:latest
    restart: unless-stopped
    volumes:
      - /mnt/syrah/homarr/config:/app/data/configs
      - /mnt/syrah/homarr/icons:/app/public/icons
    ports:
      - '7575:7575'

Manicraft1001•14mo ago

The second error is the same as this issue: https://github.com/ajnart/homarr/issues/1428 That should be resolved soon. However I don't know why we get this weird error recently (error one). @Meierschlumpf do you have any idea?

GitHub

Unexpected error has occurred · Issue #1428 · ajnart/homarr

Environment Docker Version Latest beta (26.09.2023) Describe the problem When loading up the page after starting it using docker-compose I get the following error: An unexpected error has occurred ...

Meierschlumpf•14mo ago

Nope sorry, I don't know what is the issue

LeahOP•14mo ago

I noticed if I blocked the Weather API request, it will delay the ECONNRESET error, I don't know if there's any correlation It doesn't seem like the weather widget loads at all

Manicraft1001•14mo ago

Is this maybe related to Prisma and the sqlite connection limit? https://github.com/vercel/next.js/issues/51605#issuecomment-1681004679 @Meierschlumpf what do you think? Is that possible? Is it even worth fixing when we are moving to drizzle anyway?

GitHub

[Error 500] "Socket Hang Up" Randomly Occurring on any Routes in Pr...

Verify canary release I verified that the issue exists in the latest Next.js canary release Provide environment information Operating System: Platform: darwin Arch: x64 Version: Darwin Kernel Versi...

Meierschlumpf•14mo ago

Idk, I guess it would be the easiest if we just try it again with drizzle when it has been merged. In my opinion it makes no sense to fix it, especially when the drizzle stuff will be merged soon

Serenaphic•14mo ago

I'm a bit confused, you're not trying to deploy the dev version are you? Only the latest? If you are then the image you're looking for for arm is here https://github.com/ajnart/homarr/pkgs/container/homarr/126241383?tag=latest Under OS / Arch, take the arm/v7 or arm64 depending on your needs

LeahOP•14mo ago

That's weird, cause when I got the docker image last time, it said homarr:dev..., not the homarr:0.13.4 Let me try it and see w3hat comes back But I was using homarr:latest when I encountered the ECONNRESET error Yep, this is the last one I pulled: ghcr.io/ajnart/homarr:dev@sha256:a1c2657c4c1e87a6d4ff0ef01e3dda23298d451b6bc842da7ccb7c71a82fe811 Pulled the image again for arm64 till getting the same error:

Listening on port 7575 url: http://95817cfc2673:7575
Error: 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://95817cfc2673:7575
Error: 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'
}

Manicraft1001•14mo ago

Did you ever configure your dashboard or is it empty / new? It could also be related to SSR fetching but I doubt that this is the case here.

LeahOP•14mo ago

It's completely brand new. Sometimes it errors after I attempt to exit and save or it'll error as soon as I load the webpage.

LeahOP•14mo ago

Here's the console, this is where I found the Weather request and tried blocking it to find the problem:

LeahOP•14mo ago

I went ahead and recorded everything from pulling the image and creating the stack to deploying it. It seems like it's less about what I do in Homarr, cause as soon as I could deploy it and check the logs it already errored.

LeahOP•14mo ago

It seems like I should just cut my losses 😅

Solution

Manicraft1001•14mo ago

We did merge the Drizzle PR... Can you delete the database and re-try?

Manicraft1001•14mo ago

If dev image is still not working it might be related to Nextjs itself...

LeahOP•14mo ago

Like re-pull the image?

Manicraft1001•14mo ago

Yes

LeahOP•14mo ago

In a meeting, I'll ping you as soon as I can try

Manicraft1001•14mo ago

Yea, no problem I'll be off in 20 minutes. So I might already be sleeping. Just FYI

LeahOP•14mo ago

Seems to be working perfectly! I don't know if I should keep this open until EoW or just close it out now, but so far I haven't encountered the ECONNRESET yet. I did find a different error, but it's not program breaking and I can post it in a new thread if no one's mentioned it already. <:cheebs_thumbs_up:929088326324060160>

Meierschlumpf•14mo ago

Sounds good

Manicraft1001•14mo ago

Nice, glad that it's fixed now Yes, please open a new post

Gaming

Programming

"ECONNRESET" all the bugs!