Skip to content
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

webapp-conversation set inputs have 500 error #11811

Closed
5 tasks done
xs818818 opened this issue Dec 18, 2024 · 4 comments
Closed
5 tasks done

webapp-conversation set inputs have 500 error #11811

xs818818 opened this issue Dec 18, 2024 · 4 comments
Labels
🐞 bug Something isn't working 🌚 invalid This doesn't seem right

Comments

@xs818818
Copy link

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.14.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

2024-12-18 20-48-47屏幕截图
2024-12-18 20-48-58屏幕截图

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added the 🐞 bug Something isn't working label Dec 18, 2024
Copy link

dosubot bot commented Dec 18, 2024

I found a similar open issue related to a 500 error in the Dify webapp-conversation module. The suggested solution involves checking several configurations and environment variables in your Docker setup:

  1. API URLs: Ensure that all API URLs are correctly set and accessible.
  2. Enable Debugging: Set DEBUG=true and FLASK_DEBUG=true to get more detailed error messages.
  3. Database Configuration: Verify that your PostgreSQL database configuration is correct.
  4. Redis Configuration: Ensure your Redis configuration is correct.
  5. Celery Configuration: Check your Celery broker URL.
  6. CORS Configuration: Ensure CORS settings are correctly configured.
  7. Storage Configuration: Verify that the storage path is correctly set and accessible.
  8. Sentry Configuration: If using Sentry, ensure the DSN is correctly set.

After verifying and updating these configurations, restart your Docker containers to apply the changes. This should help resolve the "Internal Server Error" you are encountering [1].

To continue talking to Dosu, mention @dosu.


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

@crazywoola
Copy link
Member

Please provide the logs of the web page.

@crazywoola crazywoola added the 🌚 invalid This doesn't seem right label Dec 19, 2024
@xs818818
Copy link
Author

2024-12-19 16-37-04屏幕截图
2024-12-19 16-37-32屏幕截图

@crazywoola
Copy link
Member

It seems you are running the project with source code? But you labeled with docker, so I am a little bit confused here. Can you clarify this?
The error code 502 suggest the backend does not start correctly, please check the backend logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working 🌚 invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants