[Bug] logto and database are broken since last X updates

[AbondonedScrawl]

📦 Environment

Docker

📌 Version

latest

💻 Operating System

Ubuntu

🌐 Browser

Chrome, Safari

🐛 Bug Description

Since a couple of updates ago, logto stoped working with following error message:

> logto db alt deploy
Error: Missing target version
    at getTargetVersion (file:///etc/logto/packages/cli/lib/commands/database/alteration/version.js:42:39)
    at chooseAlterationsByVersion (file:///etc/logto/packages/cli/lib/commands/database/alteration/version.js:58:33)
    at Object.handler (file:///etc/logto/packages/cli/lib/commands/database/alteration/index.js:88:43)
Specify --help for available options

Now database is throwing this message aswell:

[auth][error] r2: "response" is not a conform Authorization Server Metadata response (unexpected HTTP status code)
    at r5 (/app/.next/server/chunks/43505.js:368:4893)
    at ne (/app/.next/server/chunks/43505.js:368:6924)
    at iB (/app/.next/server/chunks/43505.js:368:46968)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async iG (/app/.next/server/chunks/43505.js:368:49798)
    at async i0 (/app/.next/server/chunks/43505.js:368:52440)
    at async i2 (/app/.next/server/chunks/43505.js:368:56596)
    at async /app/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]_react-d_1cf2c798572f9d55dae58de467e3f455/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:36932
    at async eC.execute (/app/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]_react-d_1cf2c798572f9d55dae58de467e3f455/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27548)
    at async eC.handle (/app/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]_react-d_1cf2c798572f9d55dae58de467e3f455/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:38186)
[NextAuth] Error: {
  cause: 'Configuration',
  message: 'Wrong configuration, make sure you have the correct environment variables set. Visit https://lobehub.com/docs/self-hosting/advanced/authentication for more details.',
  name: 'NextAuth Error'
}

I ignored this issue as I had active session where I could continue using agents. However, now that I need to login it seems impossible.

Whew trying to login I get this error:

I use this docker compose file: https://raw.githubusercontent.com/lobehub/lobe-chat/HEAD/docker-compose/local/setup.sh

📷 Recurrence Steps

Use docker compose example

🚦 Expected Behavior

Working authentication, correct configuration of containers

📝 Additional Information

No response

[lobehubbot]

👀 @AbondonedScrawl

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

I found a similar unsolved discussion regarding issues with Docker Compose deployment in Lobe Chat, which might be related to your problem. You can check it out here ^[1].

For the issues you're facing, here are some troubleshooting steps and information that might help:

1. Missing Target Version Error: This error suggests that the logto command is unable to determine the target version for database alterations. Unfortunately, I couldn't find specific details on how the versioning system works in the logto command within the repository. You might want to check if there are any recent changes or updates in the logto and database components that could affect this functionality.

2. Unexpected HTTP Status Code: This error in the authentication module could be due to misconfigured environment variables. Ensure that all required environment variables for authentication are correctly set. You can refer to the detailed list of required environment variables for proper authentication configuration in Lobe Chat ^[2].

3. "Oops, something went wrong" Error: This error message often indicates a configuration issue. Common configuration errors that lead to this message weren't specifically detailed in the repository, but ensuring that all environment variables and service dependencies are correctly configured in your Docker Compose setup is crucial.

4. Docker Compose Setup: Recent changes in the Docker Compose setup might affect authentication and database functionality. Ensure that your setup aligns with the latest configurations, such as the integration of Casdoor for authentication and the use of PostgreSQL for database services ^[3][4].

5. Authentication Troubleshooting: Verify that your authentication setup is correct by checking the environment variables and ensuring that the user ID is properly extracted and set in the context. If you're using Authentik SSO, make sure the Redirect URL/Origin matches your deployed URL ^[5].

Review these points and adjust your configuration accordingly. If the issue persists, consider checking for any updates or patches that might address these specific problems.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[SpeedupMaster]

It seems to be a logto issue. You can try reverting to the version before the update. logto requires a manual database update before each update.

[AbondonedScrawl]

That introduces an outdated container in an environment. That might one day become low-hanging fruit.

[fqscfqj]

“This is caused by the logto update, logto was updated to version 1.20.0 today. There are two solutions:

Continue to use version v1.19.0
Enter the logto container and run the following command to deploy the database changes:
npm run alteration deploy”

Only keep the lobe-postgres and lobe-logto containers running. After restarting the lobe-logto container, quickly enter the command line to execute commands and switch the database. Remember to back up the data in advance.

[AbondonedScrawl]

This solves the issue, however it implies using outdated logto container. Are there any solutions planned to fix this?This solves the issue, however it implies using outdated logto container. Are there any solutions planned to fix this?

[arvinxx]

you need to ask the issue in logto, or just move to other auth provider like casdoor

[AbondonedScrawl]

Thanks. Do you happen to have notes for casdoor? Current build feels a bit fragile (due to using older versions), I will probably spend a good week trying to figure out it myself. I'm not dev.

[AbondonedScrawl]

[SpeedupMaster]

Please refer to the official documentation of logto to update logto. ref

[charIeszhao]

The answer is pretty obvous:

Error: Missing target version

You need to specify the target version in the CLI command...

So instead of:

logto db alt deploy

You should use

logto db alt deploy <target_version_number>

[AbondonedScrawl]

It's not obvious to me because I'm not a dev.