-
-
Notifications
You must be signed in to change notification settings - Fork 395
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
bug: 'Internal Server Error' with no more error information #4911
Comments
Is there any startup command argument that outputs more logs? Thanks. |
Hi @kidlj , I just tested with your setup, but when I run It's strange that you can seed your db with a role with insufficient permission and I cannot reproduce your situations. Please provide more context, or reach out in our Discord channel to see if we can help you pinpoint the issue. |
@xiaoyijun Thank you for the help and sorry for not providing sufficient information to reproduce. I was using PostgreSQL 13 which is OK to seed db, but from PostgreSQL 15+ on, you must grant permission on PUBLIC schema to Logto user.
will fix this. I have tested with PostgreSQL 13 and PostgreSQL 16, both resulted in the same 'Internal Server Error'. |
Hi @kidlj , I just tested the way you have done, and it works on my machine. ![]() |
@kidlj , I deployed Logto as per your instructions, but I still couldn't reproduce the issue you mentioned. Maybe it's worth checking if there are other reasons. Here are the steps I took to deploy Logto:
GRANT ALL ON SCHEMA public TO logto;
version: "3.9"
services:
app:
image: svhd/logto:1.11
entrypoint: ["sh", "-c", "npm run cli db seed -- --swe && npm start"]
ports:
- 3001:3001
- 3002:3002
environment:
- TRUST_PROXY_HEADER=1
- DB_URL=postgres://logto:logto@host.docker.internal:5432/logto
- ENDPOINT=https://${MYCUSTOM_AUTH_DOMAIN}
- ADMIN_ENDPOINT=https://${MYCUSTOM_ADMIN_DOMAIN} xiaoyijun@xiaoyijunAtSilverhand logto-bug-inspect % docker compose up
[+] Running 1/1
⠿ Container logto-bug-inspect-app-1 Recreated 0.1s
Attaching to logto-bug-inspect-app-1
logto-bug-inspect-app-1 |
logto-bug-inspect-app-1 | > cli
logto-bug-inspect-app-1 | > logto db seed --swe
logto-bug-inspect-app-1 |
logto-bug-inspect-app-1 | - Create tables
logto-bug-inspect-app-1 | info ✔ Create tables
logto-bug-inspect-app-1 | info ✔ [default] Generated config oidc.privateKeys
logto-bug-inspect-app-1 | info ✔ [default] Generated config oidc.cookieKeys
logto-bug-inspect-app-1 | info ✔ [default] Seed OIDC config
logto-bug-inspect-app-1 | info ✔ [admin] Generated config oidc.privateKeys
logto-bug-inspect-app-1 | info ✔ [admin] Generated config oidc.cookieKeys
logto-bug-inspect-app-1 | info ✔ [admin] Seed OIDC config
logto-bug-inspect-app-1 | info ✔ Cloud Service Application successfully created for: default
logto-bug-inspect-app-1 | info ✔ Seed data
logto-bug-inspect-app-1 | npm notice
logto-bug-inspect-app-1 | npm notice New major version of npm available! 9.8.1 -> 10.2.4
logto-bug-inspect-app-1 | npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.2.4>
logto-bug-inspect-app-1 | npm notice Run `npm install -g npm@10.2.4` to update!
logto-bug-inspect-app-1 | npm notice
logto-bug-inspect-app-1 |
logto-bug-inspect-app-1 | > start
logto-bug-inspect-app-1 | > cd packages/core && NODE_ENV=production node .
logto-bug-inspect-app-1 |
logto-bug-inspect-app-1 | (node:44) ExperimentalWarning: Import assertions are not a stable feature of the JavaScript language. Avoid relying on their current behavior and syntax as those might change in a future version of Node.js.
logto-bug-inspect-app-1 | (Use `node --trace-warnings ...` to show where the warning was created)
logto-bug-inspect-app-1 | (node:44) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
logto-bug-inspect-app-1 | warn [CACHE] No Redis client initialized, skipping
logto-bug-inspect-app-1 | info Core app is running at http://localhost:3001/
logto-bug-inspect-app-1 | info Core app is running at https://auth.***.***/
logto-bug-inspect-app-1 | info Admin app is running at http://localhost:3002/
logto-bug-inspect-app-1 | info Admin app is running at https://admin.***.***/
logto-bug-inspect-app-1 | info Init tenant: admin
logto-bug-inspect-app-1 | <-- GET /
logto-bug-inspect-app-1 | --> GET / 302 13ms 63b
logto-bug-inspect-app-1 | <-- GET /console/welcome
logto-bug-inspect-app-1 | --> GET /console/welcome 200 36ms 358b ![]() And the docker containers is as follows: ![]() Logto works fine, please check if there are other reasons. |
It must be a docker-proxy related issue, since the symptom is the same as the issue(nothing but simply 500 Internal Server Error). @xiaoyijun Thanks for your help. |
Describe the bug
I deploy Logto in a docker container, connecting to a standalone database with a dedicated DB user. The DB seeding process is fine, and Logto startup is also fine. But when accessing the admin dashboard, it always shows 'Internal Server Error' with no more error message or logs.
I tested with the official
docker-compose.yml
which connects to a containered Postgresql usingpostgres
user, and it works fine.Expected behavior
No internal server error.
How to reproduce?
Context
Screenshots
The text was updated successfully, but these errors were encountered: