H
Homarr12mo ago
Killian

don't work after update.

[Symbol(realm)]: { settingsObject: {} }, [Symbol(state)]: { aborted: false, rangeRequested: false, timingAllowPassed: false, requestIncludesCredentials: false, type: 'default', status: 500, timingInfo: null, cacheState: '', statusText: 'Internal Server Error', headersList: HeadersList { cookies: null, [Symbol(headers map)]: Map(4) { 'connection' => { name: 'connection', value: 'close' }, 'date' => { name: 'date', value: 'Fri, 10 Nov 2023 23:21:19 GMT' }, 'keep-alive' => { name: 'keep-alive', value: 'timeout=5' }, 'transfer-encoding' => { name: 'transfer-encoding', value: 'chunked' } }, [Symbol(headers map sorted)]: null }, urlList: [],  { stream: <ref *1> ReadableStream { _state: 'closed', _reader: ReadableStreamDefaultReader { _ownerReadableStream: [Circular *1], _closedPromise_resolve: undefined, _closedPromise_reject: undefined, _closedPromise: Promise { }, _readRequests: S { _cursor: 0, _size: 0, _front: { _elements: [], _next: undefined }, _back: { _elements: [], _next: undefined } } }, _storedError: undefined, _disturbed: true, _readableStreamController: ReadableStreamDefaultController { _controlledReadableStream: [Circular *1], _queue: S { _cursor: 0, _size: 0, _front: { _elements: [], _next: undefined }, _back: { _elements: [], _next: undefined } }, _queueTotalSize: 0, _started: true, _closeRequested: true, _pullAgain: false, _pulling: true, _strategySizeAlgorithm: undefined, _strategyHWM: 0, _pullAlgorithm: undefined, _cancelAlgorithm: undefined } }, source: null, length: null } }, [Symbol(headers)]: Headers { [Symbol(headers list)]: HeadersList { cookies: null, [Symbol(headers map)]: Map(4) { 'connection' => { name: 'connection', value: 'close' }, 'date' => { name: 'date', value: 'Fri, 10 Nov 2023 23:21:19 GMT' }, 'keep-alive' => { name: 'keep-alive', value: 'timeout=5' }, 'transfer-encoding' => { name: 'transfer-encoding', value: 'chunked' } }, [Symbol(headers map sorted)]: null }, [Symbol(guard)]: 'response', [Symbol(realm)]: { settingsObject: {} } } } }, shape: undefined, data: undefined, name: 'TRPCClientError' }, elapsedMs: 18 } Error [TRPCClientError]: Unexpected token 'I', "Internal S"... is not valid JSON at TRPCClientError.from (file:///app/.next/server/src/middleware.js:1729:16) at <unknown> (file:///app/.next/server/src/middleware.js:2069:36) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [next-auth][error][CLIENT_FETCH_ERROR] https://next-auth.js.org/errors#client_fetch_error fetch failed { error: { message: 'fetch failed', stack: 'TypeError: fetch failed\n' + ' at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669)\n' + ' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)', name: 'TypeError' }, url: 'http://localhost:3000/api/auth/session', message: 'fetch failed' }
Errors | NextAuth.js
This is a list of errors output from NextAuth.js.
Solution:
This issue should be fixed with release v0.14.1 ! If not, please open up a ticket in #💬・get-help
GitHub
Release v0.14.1 Stability improvement and bug fixes · ajnart/homarr
Your issues should be resolved! During the last release, we didn't spend enough time to test on different hardware configurations to ensure that v0.14.0 would work on the majority of people'...
Jump to solution
82 Replies
Manicraft1001
Manicraft100112mo ago
Is there more in the log?
Killian
KillianOP12mo ago
for info : i don't open port (nat) on portainer, only use subdomain conf : server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name admindffghfdh.com; include /config/nginx/ssl.conf; client_max_body_size 0; location / { # enable the next two lines for http auth auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app homarr; set $upstream_port 7575; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } what's the path for log file in container ?
Manicraft1001
Manicraft100112mo ago
There is no log file in the container
Killian
KillianOP12mo ago
i have only that in portainer log :
Killian
KillianOP12mo ago
[Symbol(realm)]: { settingsObject: {} }, [Symbol(state)]: { aborted: false, rangeRequested: false, timingAllowPassed: false, requestIncludesCredentials: false, type: 'default', status: 500, timingInfo: null, cacheState: '', statusText: 'Internal Server Error', headersList: HeadersList { cookies: null, [Symbol(headers map)]: Map(4) { 'connection' => { name: 'connection', value: 'close' }, 'date' => { name: 'date', value: 'Fri, 10 Nov 2023 23:25:22 GMT' }, 'keep-alive' => { name: 'keep-alive', value: 'timeout=5' }, 'transfer-encoding' => { name: 'transfer-encoding', value: 'chunked' } }, [Symbol(headers map sorted)]: null }, urlList: [], 
{ stream: <ref *1> ReadableStream { _state: 'closed', _reader: ReadableStreamDefaultReader { _ownerReadableStream: [Circular *1], _closedPromise_resolve: undefined, _closedPromise_reject: undefined, _closedPromise: Promise { }, _readRequests: S { _cursor: 0, _size: 0, _front: { _elements: [], _next: undefined }, _back: { _elements: [], _next: undefined } } }, _storedError: undefined, _disturbed: true, _readableStreamController: ReadableStreamDefaultController { _controlledReadableStream: [Circular *1], _queue: S { _cursor: 0, _size: 0, _front: { _elements: [], _next: undefined }, _back: { _elements: [], _next: undefined } }, _queueTotalSize: 0, _started: true, _closeRequested: true, _pullAgain: false, _pulling: true, _strategySizeAlgorithm: undefined, _strategyHWM: 0, _pullAlgorithm: undefined, _cancelAlgorithm: undefined } }, source: null, length: null } }, [Symbol(headers)]: Headers { [Symbol(headers list)]: HeadersList { cookies: null, [Symbol(headers map)]: Map(4) { 'connection' => { name: 'connection', value: 'close' }, 'date' => { name: 'date', value: 'Fri, 10 Nov 2023 23:25:22 GMT' }, 'keep-alive' => { name: 'keep-alive', value: 'timeout=5' }, 'transfer-encoding' => { name: 'transfer-encoding', value: 'chunked' } }, [Symbol(headers map sorted)]: null }, [Symbol(guard)]: 'response', [Symbol(realm)]: { settingsObject: {} } } } }, shape: undefined, data: undefined, name: 'TRPCClientError' }, elapsedMs: 11 } Error [TRPCClientError]: Unexpected token 'I', "Internal S"... is not valid JSON at TRPCClientError.from (file:///app/.next/server/src/middleware.js:1729:16) at <unknown> (file:///app/.next/server/src/middleware.js:2069:36) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [next-auth][error][CLIENT_FETCH_ERROR] https://next-auth.js.org/errors#client_fetch_error fetch failed { error: { message: 'fetch failed', stack: 'TypeError: fetch failed\n' + ' at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669)\n' + ' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)', name: 'TypeError' }, url: 'http://localhost:3000/api/auth/session', message: 'fetch failed' }
Errors | NextAuth.js
This is a list of errors output from NextAuth.js.
Killian
KillianOP12mo ago
not more
Manicraft1001
Manicraft100112mo ago
As an information for you: It's almost 01:00 (1AM) in my timezone. Therefore, any further support from the Homarr team will resume next day (in about 7-8 hours). Make sure that you followed the onboarding instructions and added the mount point
Killian
KillianOP12mo ago
yeah not prob! i've checked, and all was ok !
BlackSpirit
BlackSpirit12mo ago
Hi there, had some issue with my reverse proxy, ended up having to add a location block to my config for the api routes that excludes auth essentially
location ~ /api {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app homarr;
set $upstream_port 7575;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;

}
location ~ /api {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app homarr;
set $upstream_port 7575;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;

}
hope this helps ya
Killian
KillianOP12mo ago
i'll try but same error! but thanks
Tag
Tag12mo ago
url: 'http://localhost:3000/api/auth/session',
url: 'http://localhost:3000/api/auth/session',
That looks like this shouldn't be the right address. Normally you should be on port 7575 and I doubt that you changed that. I think it's trying to fetch on 3000 but you are indeed using 7575 so nothing is there. Try setting your port to 3000 temporarily
Thomas
Thomas12mo ago
@Killian what’s your docker compose setup looking like ?
sicario0
sicario012mo ago
Hi, i have the same error after updating through Portainer and i haven't changed anything in my docker-compose file or anywhere else^^
Tag
Tag12mo ago
If you haven't changed you docker-compose, then there lies the problem. https://homarr.dev/blog/2023/11/10/authentication#breaking-changes There's a new mounting point necessary for the database of users.
sicario0
sicario012mo ago
it's working it was my fault indeed i am sorry! thanks! 🙂
JIMSL1CE
JIMSL1CE12mo ago
Adding a <path-to-data>:/data bind-mount to my compose fixed the issue.
lafours23
lafours2312mo ago
So I tried this with unraid and it still didn't work, is there a specific path for /data
Manicraft1001
Manicraft100112mo ago
Can you post your mount point in Unraid (screenshot of the configuration and paths)?
Thomas
Thomas12mo ago
Also try setting an env variable of NEXTAUTH_URL=http://localhost:7575/ and see if that helps
Tag
Tag12mo ago
If anyone has further issues, please make a different get-help ticket. @Killian Can you tell us if your docker compose is up to date and what environment you're using? (like cpu architecture, OS), Also try ajnart's suggestion.
Killian
KillianOP12mo ago
I will answer after, I haven’t accès portainer : but I can say I use docker, I check env and all was ok. And no file was created after update on db folder
Tag
Tag12mo ago
There might be a permission problem, if no database file was created after starting the container Get to it when you have time
Manicraft1001
Manicraft100112mo ago
As a note: I will implement a permission check that checks if the database file was mounted 🙂
Tag
Tag12mo ago
Would be great. Maybe some checks for the config too. I know it happened a few times as well
Manicraft1001
Manicraft100112mo ago
Will do it today 👍
Tag
Tag12mo ago
0.14.1 for tomorrow at this rate lol Back to the ticket though, we're straying from the main subject sorry
Big Hyuge
Big Hyuge12mo ago
My compose file.
version: '3'
services:
homarr:
container_name: homarr
image: ghcr.io/ajnart/homarr:latest
restart: unless-stopped
volumes:
#- /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
- ./homarr/configs:/app/data/configs
- ./homarr/icons:/app/public/icons
- ./homarr/data:/data
#environment:
ports:
- '7575:7575'
networks:
- proxy-network

networks:
proxy-network:
external: true
version: '3'
services:
homarr:
container_name: homarr
image: ghcr.io/ajnart/homarr:latest
restart: unless-stopped
volumes:
#- /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
- ./homarr/configs:/app/data/configs
- ./homarr/icons:/app/public/icons
- ./homarr/data:/data
#environment:
ports:
- '7575:7575'
networks:
- proxy-network

networks:
proxy-network:
external: true
Error logs
JamesC23
JamesC2312mo ago
same issue, even after adding the data mapping
fedeb🇦🇷
fedeb🇦🇷12mo ago
same issue error: { message: 'fetch failed', stack: 'TypeError: fetch failed\n' + ' at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669)\n' + ' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)', name: 'TypeError' }, url: 'http://localhost:3000/api/auth/session', message: 'fetch failed' } I instaled yestarday v13 and today upgrade to v14 and got issue
Meierschlumpf
Meierschlumpf12mo ago
Same issue as: The module '/app/node_modules/better-sqlite3/build/Release/better_sqlite3.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 108. This version of Node.js requires NODE_MODULE_VERSION 115. Please try re-compiling or re-installing ?
JamesC23
JamesC2312mo ago
#homarr homarr:
container_name: "homarr"
hostname: "homarr"
image: "ghcr.io/ajnart/homarr:latest"
ipc: "private"
labels:
- "com.centurylinklabs.watchtower.enable=true"
networks: exampleNet: ipv4_address: "172.18.5.1" # Set the desired IPv4 address
ports:
- "8080:7575/tcp"
restart: "unless-stopped"
volumes:
- "/home/example/Documents/docker-storage/homarr/icons:/app/public/icons"
- "/home/example/Documents/docker-storage/homarr:/app/data/configs"
- "/home/example/Documents/docker-storage/homarr/data:/data" working_dir: "/app"
Meierschlumpf
Meierschlumpf12mo ago
@fedeb
fedeb🇦🇷
fedeb🇦🇷12mo ago
I will just downgrade to v13 until is v14 is fixed. I dont want to try and error, since I just started using homarr
Meierschlumpf
Meierschlumpf12mo ago
You got the error with NODE_MODULE_VERSION? Because if so it should be fixed within the next release
lafours23
lafours2312mo ago
@Manicraft1001 here are the unraid settings.
No description
Thomas
Thomas12mo ago
@here We are looking for a group of people experiencing errors with the new release of homarr, if you are having issues please let @Manicraft1001 know you'd be interested in helping us fix this issue.
BlackSpirit
BlackSpirit12mo ago
How can we help?
Thomas
Thomas12mo ago
Send a message there if you are interested in helping https://discord.com/channels/972958686051962910/1173242881486635092 @BlackSpirit It would be very nice of you! @Leowen too
Killian
KillianOP12mo ago
Sorry I will unfollow that, I will continue to use organizrr and not homard good luck!
Leowen
Leowen12mo ago
Ömmm guys I think I found the problem and the possible solution for the text file busy issue 😄
Meierschlumpf
Meierschlumpf12mo ago
Okay sound nice, what seems to be the issue?
Leowen
Leowen12mo ago
GitHub
Node 20.3.0 images give error `/usr/bin/env: 'node': Text file busy...
Environment Platform: macos 13.4 M1 Docker Version: 24.0.2 Node.js Version: 20.3.0 Image Tag: node:20-alpine3.17 Expected Behavior yarn tsc should run correctly Current Behavior > [service 5/5] ...
Leowen
Leowen12mo ago
I downgrade the node version to 20.2 and I was able to run the migrate-ts successfully 🙂
Leowen
Leowen12mo ago
No description
Meierschlumpf
Meierschlumpf12mo ago
Interesting, so you downgraded it for yourself and created your own build?
Leowen
Leowen12mo ago
ye Okay, tbh it was not my idea, I discussed this with my friend who is a LastPass™ engineer 😄
Meierschlumpf
Meierschlumpf12mo ago
Okay @ajnart @Manicraft1001 should we then downgrade node to that version? @Leowen can you maybe also check with node:20.9.0-slim, because a upgrade would be better than a downgrade
Leowen
Leowen12mo ago
ofc just a minute nope not working with that
Meierschlumpf
Meierschlumpf12mo ago
Okay I'll have to ask the other contributors how we continue with that issue
Thomas
Thomas12mo ago
Yeah if it works I don’t care about node version It’s funny every time we upgrade node it fucks up stuff
Leowen
Leowen12mo ago
its like a Windows Update 😄
Meierschlumpf
Meierschlumpf12mo ago
So node:20-alpine3.16 works for you? Or which version you were using for testing?
Leowen
Leowen12mo ago
v20.2.0
Leowen
Leowen12mo ago
No description
Meierschlumpf
Meierschlumpf12mo ago
Yes but which image within docker
Leowen
Leowen12mo ago
node-v20.2.0-linux-x64
Meierschlumpf
Meierschlumpf12mo ago
Can you try 20.2.0-slim, we were using slim currently @Leowen
Leowen
Leowen12mo ago
Im trying 😄 slim builds are not available in nvm :/
Leowen
Leowen12mo ago
No description
Meierschlumpf
Meierschlumpf12mo ago
Oh you were using nvm, makes sense then
Leowen
Leowen12mo ago
sorry, i forgot to mention
Meierschlumpf
Meierschlumpf12mo ago
We will release with 20.2.0-slim and if it doesn't work just notify us again so we can debug together
Leowen
Leowen12mo ago
Okay 😄
Manicraft1001
Manicraft100112mo ago
Yes
Leowen
Leowen12mo ago
which image should i use? Im not sure
Meierschlumpf
Meierschlumpf12mo ago
You will be able to use latest as soon as we have released
Leowen
Leowen12mo ago
ahh, okay 😄
Leowen
Leowen12mo ago
No description
Leowen
Leowen12mo ago
🙂
Meierschlumpf
Meierschlumpf12mo ago
Thats on dev now, right?
Leowen
Leowen12mo ago
yep
Meierschlumpf
Meierschlumpf12mo ago
Nice 🔥🚀
Leowen
Leowen12mo ago
it works! \o/
Meierschlumpf
Meierschlumpf12mo ago
We will release 0.14.1 tomorrow, because it's already late
Thomas
Thomas12mo ago
Yeah, I'll remove the prints nevermind
Meierschlumpf
Meierschlumpf12mo ago
No they are good. It's only during onboard
Thomas
Thomas12mo ago
It's in onboarding not trpc, i thought. Like when it said "constructing interal address" like 100 times x)
Meierschlumpf
Meierschlumpf12mo ago
xD
Leowen
Leowen12mo ago
honestly guys, this was not my easiest start with an app, but the support is truly amazing 😄 Thanks for all pepelove
Solution
Thomas
Thomas12mo ago
This issue should be fixed with release v0.14.1 ! If not, please open up a ticket in #💬・get-help
GitHub
Release v0.14.1 Stability improvement and bug fixes · ajnart/homarr
Your issues should be resolved! During the last release, we didn't spend enough time to test on different hardware configurations to ensure that v0.14.0 would work on the majority of people'...
Want results from more Discord servers?
Add your server