DB版出现同账户配置不同

[Roiung]

📦 部署环境

Docker

📦 部署模式

服务端模式(lobe-chat-database 镜像)

📌 软件版本

1.59.0

💻 系统环境

Ubuntu

🌐 浏览器

Edge

🐛 问题描述

DB版，原本手机浏览器端和电脑Edge浏览器端用同一账号进去，添加的智能助手，对话记录能够完全一致，两边基本上是同步状态。前面电脑浏览器出了点问题，用删除浏览记录选项，将全部记录清空以后，电脑浏览器登陆进去后，所有添加的智能助手和对话记录都没了。账号确定是同一个账号，手机上相关信息都还在，请问这是什么情况？现在有什么办法能够恢复？

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[lobehubbot]

👀 @Roiung

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。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

📦 Deployment environment

Docker

📦 Deployment Mode

Server-side mode (lobe-chat-database mirror)

📌 Software version

1.59.0

💻 System environment

Ubuntu

🌐 Browser

Edge

🐛 Question description

DB version, the original mobile browser and computer Edge browser are used to enter the same account, and the added smart assistant can be completely consistent in the dialogue records, and the two sides are basically in a synchronous state. There was something wrong with the computer browser in front. After using the option to delete browsing history, after the computer browser logs in, all the added smart assistants and dialogue records are gone. The account is confirmed to be the same account, and the relevant information on the mobile phone is still there. What is the situation? Is there any way to recover now?

📷 Reproduction steps

No response

🚦 Expected results

No response

📝 Supplementary information

No response

[dosubot[bot]]

Hello @Roiung! I'm here to assist you with any bugs, questions, or contributions. Let's work together to resolve the issue you're experiencing.

I found a similar closed issue that might be relevant to your problem. The suggested solution involves several steps to address the issue of assistants and message logs disappearing in Lobe Chat:

1. Check Network Connection: Ensure your device has a stable network connection, as data synchronization relies on the network.

2. Data Synchronization Issue: Lobe Chat uses WebRTC for data synchronization. Ensure all devices are online simultaneously for synchronization. If devices are on different networks, it may cause synchronization failure.

3. Browser Cache: Try clearing the browser cache and then reload the page.

4. IndexedDB Database: Lobe Chat uses IndexedDB locally to store data. You can check the browser's developer tools to see if the data exists in IndexedDB.

5. Server-side Database: If you are using a server-side database (such as PostgreSQL), check the database connection and data integrity.

6. Error Logs: Check the browser console or server logs for any related error messages, which may help diagnose the issue.

These steps might help you recover the missing data or understand why it disappeared ^[1].

To continue talking to Dosu, mention @dosu.

---

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

[Roiung]

日志提示如下：
stderr: [31m[auth][details][0m: {}
stderr: [31m[auth][error][0m AdapterError: Read more at https://errors.authjs.dev#adaptererror
stderr: [31m[auth][cause][0m: error: insert or update on table "agents" violates foreign key constraint "agents_user_id_users_id_fk"
stderr: at /app/node_modules/.pnpm/[email protected]/node_modules/pg/lib/client.js:535:17
stderr: at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
stderr: at async /app/.next/server/chunks/76859.js:17:13032
stderr: at async /app/.next/server/chunks/65918.js:1:3598
stderr: at async y.transaction (/app/.next/server/chunks/76859.js:17:14301)
stderr: at async p.createInbox (/app/.next/server/chunks/65918.js:1:4079)
stderr: at async d.createInbox (/app/.next/server/chunks/65918.js:1:9783)
stderr: at async createUser (/app/.next/server/chunks/96136.js:1:18316)
stderr: at async r. (/app/.next/server/chunks/87486.js:1:45812)
stderr: at async rK (/app/.next/server/chunks/87486.js:368:3147)
stderr: [31m[auth][details][0m: {}
stdout: [rewrite] /next-auth/error -> http://127.0.0.1:3210/zh-CN__0__dark/next-auth/error
stdout: [rewrite] / -> http://127.0.0.1:3210/zh-CN__0__dark

[Roiung]

找到原因了，清除掉浏览器记录之后，用原有账号登录会导致pg数据库中casdoor库中user表的id至发生变化，产生了一个新的id，然后在lobe库中，新的id跟lobe库中的agent和user中的id都对不上，就相当于变成了一个新账号。从agent表中复制id到casdoor中修改，再登陆就OK了。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

The reason was found. After clearing the browser record, logging in with the original account will cause the id of the user table in the casdoor library in the pq database to change, resulting in a new id. Then in the lobe library, the new id and lobe If the agent in the library and the id in the user are not in line with each other, it is equivalent to becoming a new account. Copy the id from the agent table and modify it in casdoor, and then log in.

[Roiung]

神奇的是这个问题不是每次都能出现，我前不久出现过一次，当时数据少，我重新搭环境了。这次恢复数据后，我想再次复现，我清空多次浏览器数据后再没出现过，不知何故。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

The magical thing is that this problem does not occur every time. I happened to it not long ago. At that time, there was little data and I re-built the environment. After recovering the data this time, I wanted to reproduce it again. I cleared the browser data several times and never appeared again, for some reason.