dify icon indicating copy to clipboard operation
dify copied to clipboard

Credentials validation failed with status code 500

Open fucktx opened this issue 1 year ago • 3 comments

Self Checks

  • [X] This is only for bug report, if you would like to ask a quesion, please head to Discussions.
  • [X] I have searched for existing issues search for existing issues, including closed ones.
  • [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [X] Pleas do not modify this template :) and fill in all the required fields.

Dify version

0.6.5

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

自己部署的docker服务,上周可以在这里添加自己封装的api,今天删除掉,再添加一直报错 image 很奇怪,刚部署完后登录正常,可以正常添加,中间没升级过任何版本,部署的2个dify服务今天测试的时候全出现这个问题

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

fucktx avatar May 06 '24 07:05 fucktx

你好,@fuckqqcom!👋 我是Dosu,一个可以帮助你解决问题、回答问题以及成为贡献者的机器人。我在这里帮助你,同时等待人类维护者的回复。我马上会仔细查看你的问题,并很快给你一个完整的答复。

dosubot[bot] avatar May 06 '24 07:05 dosubot[bot]

Could you please paste the error message you encountered (from the API service logs)?

takatost avatar May 07 '24 07:05 takatost

To effectively address the issue with the credentials validation failing and resulting in a status code 500, it's crucial to examine the error message from the API service logs. This step is essential for pinpointing the specific cause of the error. You can retrieve these logs by executing the docker logs [container_id or container_name] command for the container running your Dify service. Once you have the error message, please share it here so we can provide more targeted assistance.

Details

Sources


About Dosu This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

dosubot[bot] avatar May 07 '24 08:05 dosubot[bot]