thunderhub icon indicating copy to clipboard operation
thunderhub copied to clipboard

Thunderhub crashes after login

Open Wired4ncer opened this issue 2 years ago • 2 comments

With newest version, Thunderhub doesn't load when I input password in. It reloads back to login page. Log does show error.

5.15.0-82-generic #91-Ubuntu SMP Mon Aug 14 14:14:14 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  • Version of ThunderHub: 0.13.21
  • Deployment method - manual install via npm using minibolt guide https://v2.minibolt.info/lightning/lightning/web-app

Expected behavior Login and open Thub web interface.

Actual behavior Page reloads back to login window.

Log details:

Started Thunderhub.
: (node:1318006) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
: (Use `node --trace-deprecation ...` to show where the warning was created)
: upstream image response failed for /assets/amboss_icon.png TypeError: fetch failed
:     at Object.fetch (/home/thunderhub/thunderhub/node_modules/next/dist/compiled/undici/index.js:1:26669)
:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
:     at async invokeRequest (/home/thunderhub/thunderhub/node_modules/next/dist/server/lib/server-ipc/invoke-request.js:17:12)
:     at async /home/thunderhub/thunderhub/node_modules/next/dist/server/next-server.js:359:35
:     at async imageOptimizer (/home/thunderhub/thunderhub/node_modules/next/dist/server/image-optimizer.js:537:13)
:     at async cacheEntry.imageResponseCache.get.incrementalCache (/home/thunderhub/thunderhub/node_modules/next/dist/server/next-server.js:598:60)
:     at async /home/thunderhub/thunderhub/node_modules/next/dist/server/response-cache/index.js:99:36 {
:   cause: Error: connect ECONNREFUSED 127.0.0.1:3000
:       at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
:     errno: -111,
:     code: 'ECONNREFUSED',
:     syscall: 'connect',
:     address: '127.0.0.1',
:     port: 3000
:   }
: }
: ImageError: "url" parameter is valid but upstream response is invalid
:     at imageOptimizer (/home/thunderhub/thunderhub/node_modules/next/dist/server/image-optimizer.js:549:19)
:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
:     at async cacheEntry.imageResponseCache.get.incrementalCache (/home/thunderhub/thunderhub/node_modules/next/dist/server/next-server.js:598:60)
:     at async /home/thunderhub/thunderhub/node_modules/next/dist/server/response-cache/index.js:99:36 {
:   statusCode: 500
: }

Wired4ncer avatar Aug 31 '23 23:08 Wired4ncer

I have the same issue regarding "upstream image response failed for /assets/amboss_icon.png TypeError: fetch failed". As far as I can see, this issue in my environment is caused by ThunderHub connecting to a wrong port. I have different port defined in .env, however it is trying to fetch from 3000: "[upstream image response failed for /assets/amboss_icon.png TypeError: fetch failed](cause: Error: connect ECONNREFUSED 127.0.0.1:3000)"

MButcho avatar Sep 09 '23 10:09 MButcho

This error is happening for me again in the newest version 0.13.29 Was there any reason it started to happen again? Anyone found solution?

Wired4ncer avatar Dec 31 '23 02:12 Wired4ncer