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

Workflow 403 Forbidden #12896

Closed
5 tasks done
gongshaojie12 opened this issue Jan 21, 2025 · 2 comments
Closed
5 tasks done

Workflow 403 Forbidden #12896

gongshaojie12 opened this issue Jan 21, 2025 · 2 comments
Labels
🤔 cant-reproduce We can not reproduce it or the information is limited 🌊 feat:workflow Workflow related stuff. 🌚 invalid This doesn't seem right

Comments

@gongshaojie12
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.15.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When I create and publish the workflow then click Run, the page shows a 403 Forbidden error.How do I fix this problem? Thanks.

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added 🌊 feat:workflow Workflow related stuff. 🐞 bug Something isn't working labels Jan 21, 2025
Copy link

dosubot bot commented Jan 21, 2025

To resolve the 403 Forbidden error when creating and publishing a workflow and then clicking Run in a self-hosted Dify version 0.15.0 using Docker, ensure that the domain you are accessing is listed in the squid.conf file. Follow these steps:

  1. Check if your domain is listed in squid.conf.
  2. Run curl tests from inside the Docker container to verify connectivity.
  3. Ensure proper configuration of the domain in squid.conf.

This configuration is necessary when accessing HTTPS URLs with non-standard ports [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 crazywoola added 🌚 invalid This doesn't seem right 🤔 cant-reproduce We can not reproduce it or the information is limited and removed 🐞 bug Something isn't working labels Jan 21, 2025
@crazywoola
Copy link
Member

Check the environment settings and you network policies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤔 cant-reproduce We can not reproduce it or the information is limited 🌊 feat:workflow Workflow related stuff. 🌚 invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants