Backend error when clicking Setting - Account after upgrade to v1.1.1

[hikae]

Describe the bug
When clicking on Setting - Account, the backend interface "answer/api/v1/connector/user/info" returns an error. The response data is:
{"code": 500,"reason": "base.database_error", "msg": "Data server error.", "data": null}

This problem did not exist before. The error started happening after upgrading from v1.1.0 to v1.1.1. The deployment platform is Docker.

To Reproduce
Steps to reproduce the behavior:
Click on Setting - Account
The interface "answer/api/v1/connector/user/info" will return the error response above

Expected behavior
The interface "answer/api/v1/connector/user/info" should return user info data instead of error.

Platform (please complete the following information):

• Device: Desktop
• OS: Ubuntu 20.04
• Version: Upgraded from v1.1.0 to v1.1.1

Since my native language is not English, this issue was written with the assistance of an AI. Please let me know if there are any errors that need correcting.

[LinkinStars]

@hikae Sorry, if you have configured any connector plugins? Can you provide a log message of the error that occurred?

[hikae]

@hikae Sorry, if you have configured any connector plugins? Can you provide a log message of the error that occurred?

@LinkinStars No, I have not configured the connector plugin.

Here is the log

[LinkinStars]

@hikae From the logs, it appears that the problem is caused by the user_external_login table not existing. The strange thing is that this table should have been created in v1.0.5. You can try to resolve this issue by first manually doing an upgrade in the following way.

• Start and enter the docker container: docker exec -it answer bash answer is your container name.
• Execute the upgrade command manually to upgrade: answer upgrade -f v1.0.5
• If the upgrade fails in the process, please reply to the upgrade failure log.

[hikae]

@hikae From the logs, it appears that the problem is caused by the user_external_login table not existing. The strange thing is that this table should have been created in v1.0.5. You can try to resolve this issue by first manually doing an upgrade in the following way.

• Start and enter the docker container: docker exec -it answer bash answer is your container name.
• Execute the upgrade command manually to upgrade: answer upgrade -f v1.0.5
• If the upgrade fails in the process, please reply to the upgrade failure log.

@LinkinStars The issue has been resolved. Thank you very much!