-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uptime-kuma: Spliit return Internal Server Error 500 #221
Comments
Hey, Header in curl:
Header in uptime-kuma:
|
probably due to the addition of i18n modules |
See this probable root cause issue spliit-app/spliit#221 The bug was probably introduced with the following renovate upgrade 8a7ad96
Hi, Also impacted by this bug on my self hosted Kubernetes deployment. After an upgrade from NAME READY STATUS RESTARTS AGE
spliit-5648b49c6b-tdm77 0/1 Running 2 (87s ago) 11m <-- never Ready since the probe fails
# ... old versions are OK I had the same log as above ❯ kl spliit-5648b49c6b-tdm77
Setting timezone to UTC...
Waiting 60s for database to be ready...
PostgreSQL database ready!
Prisma migrate and deploy...
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "spliit", schema "public" at "spliit-postgresql:5432"
19 migrations found in prisma/migrations
No pending migrations to apply.
> [email protected] start
> next start
▲ Next.js 14.2.5
- Local: http://localhost:3000
✓ Starting...
✓ Ready in 1946ms
Error: Cannot find module './undefined.json'
at /usr/app/.next/server/chunks/3215.js:1:443
at async /usr/app/.next/server/chunks/3215.js:1:20983
at async /usr/app/.next/server/chunks/9013.js:148:9245
at async /usr/app/.next/server/chunks/9013.js:148:9710 {
code: 'MODULE_NOT_FOUND',
digest: '3224353063'
}
Error: Cannot find module './undefined.json'
... I fixed it by adding this header to my probe (see fix) livenessProbe:
httpGet:
path: /
port: http
httpHeaders:
- name: Accept-Language
value: en-US
readinessProbe:
httpGet:
path: /
port: http
httpHeaders:
- name: Accept-Language
value: en-US
startupProbe:
httpGet:
path: /
port: http
httpHeaders:
- name: Accept-Language
value: en-US I don't think this behavior is wanted, but maybe I should use another endpoint for healhtcheck.
Thanks for this great project! |
I am using uptime-kuma to monitor a few of my apps and spliit 1.9 always returns a 500 error.
This happens also if I use
curl
orwget
against my spliit instance.The logs of the spliit container contains this error:
This happens only with kuma/curl/wget but a browser works just fine so I guess there is something with the request headers perhaps.
Not really a big issue for now I accept 500 as a success
Thanks !
The text was updated successfully, but these errors were encountered: