Internal Server Error
Upgraded Homarr last night and didn't notice before I got to my work PC that it just says "Internal server error". On my phone and home PC it works but on the work PC it just says Internal Server Error.
Curl says 301 moved. Uptime-kuma also says it's offline
Logs:
2023-06-08T06:51:29.222702058Z TypeError: Cannot read properties of undefined (reading '_nextI18Next')
2023-06-08T06:51:29.222746418Z at AppWithTranslation (/app/node_modules/next-i18next/dist/commonjs/appWithTranslation.js:92:29)
2023-06-08T06:51:29.222760251Z at Wc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
2023-06-08T06:51:29.222772775Z at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
2023-06-08T06:51:29.222791698Z at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
2023-06-08T06:51:29.222803651Z at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
2023-06-08T06:51:29.222815134Z at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
2023-06-08T06:51:29.222826291Z at $c (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
2023-06-08T06:51:29.222838161Z at bd (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
2023-06-08T06:51:29.222849338Z at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
2023-06-08T06:51:29.222861141Z at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:479)
44 Replies
Hi, is that the development version?
yes
What browser do you use on all of your devices? What language?
Have you tried clearing cache on your work device?
Same chromium Vivaldi, English, yes
Tried in edge now, also Internal server error
Tried on another machine and same thing
Is the i18n error from Homarr or your browser? Any messages previous to that?
@meierschlumpf I think the upgrade yesterday broke it. Seems like it doesn't effect all machines though
i18n is from docker homarr logs
that message keeps coming up constantly and can't find any other messages. Only goes back so far
Actually more of it I forgot to copy
That again and again for at least 1000 lines
Hmm weird
It's normal that there's a warning or error... But not sure if it's normal that there are that many
You said, that it works in other browsers?
It works in the browsers I use most often, so those that are cached. If I delete cache it doesn't work anymore
Okay
I will investigate it, thanks
@spillebulle the
dev
image should be updated.
I wasn't able to reproduce, but can you check if this still happens?Yeah I saw, works fine now. Plex integration too
Awesome, thanks
❤️
@manicraft1001 Actually, just tried on my phone. Still Internal server error. Uptimekuma still says 301
PC started working, then one I deleted cache on earlier
Delete cache again and stops working
It's very weird how it displays the internal server error
Full log?
Hmm
I don't see any hint, that Homarr would be the problem
If there was a crash, there should be more information
Pulled new image again and seems fine so far
Cleared cache again and seems to be working
Weird
I don't want to fully exclude Homarr from any fault, but you you have a proxy in front of it?
Usually, internal server errors should look differently than what you showed here....
NPM
Can you check if NPM has any errors?
I don't wanna blame it on a different app, but the error message doesn't look like it comes from Homarr
Just errors from some old SSL certificates I haven't cleaned up, nothing else from the timeframe
Hmm okay
If you can find out, when the error happens, I can try to fix it
But otherwise, that will be very hard
@manicraft1001 Just got a notification from Uptime-kuma that homarr is down. I see this when I go to it
This keeps coming up again and again in the logs:
Nothing else than that for the last 1000 lines
🤔
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
I assume on dev?
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Ok, @meierschlumpf do you have an idea?
It’s so weird because everyone should have the same server.js file
I don’t understand how it can not work for some people and work for others
Not sure if we did test the production image. Might be build related...
I've got the same issue locally
Okay. Can you fix it?
If not, I will do so tomorrow 🙂
I'll try
I have absolutely no plan why this happens. I've tried to update tanstack and trpc, nextjs and my node version to 20. But I still get the same issue
Is it a known issue in one of our dependencies?
I've found something similar but nothing exactly like that:
https://github.com/TanStack/query/issues/5371
https://github.com/vercel/next.js/issues/49261
hmm
Can you pinpoint the problem causing dependency update?
no not really
Reverting it to this commit works, but not sure which upgrade is the issue
Okay
Good progress though
Hey guys can someone test the dev image ? @nicole98 @spillebulle I might've fixed it
At least it works locally now...
Works for me. I auto update with watchtowerr and it started working a few days ago
Nice
What
So it fixed itself a few days ago ?
yup