langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 12:32:54 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Cannot GET /chatbot/SBVhb8EKKnkOxeBW #12357

New Issue
Closed
opened 2026-02-21 19:07:03 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:07:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @chenzaiming123 on GitHub (Mar 30, 2025).

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

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

How to resolve the issue of the robot being inaccessible after deployment？（FOR 1.1.3 ）
tips：Cannot GET /chatbot/SBVhb8EKKnkOxeBW

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @chenzaiming123 on GitHub (Mar 30, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce How to resolve the issue of the robot being inaccessible after deployment？（FOR 1.1.3 ） tips：Cannot GET /chatbot/SBVhb8EKKnkOxeBW ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:07:03 -05:00
yindo closed this issue 2026-02-21 19:07:03 -05:00
yindo commented 2026-02-21 19:07:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 30, 2025):

I found a similar unsolved discussion that might be relevant to your issue: Help, which was last updated on March 20, 2025 [1].

For the "Cannot GET" error in Dify's self-hosted deployment, here are some troubleshooting steps you can try:

  1. Check URL Structure: Ensure that the URL structure for accessing the chatbot is correct. For Dify version 1.1.3, the expected URL structure is:

    http://localhost/chatbot/{token}?name=H4sIAKUlmWYA%2FwWAIQ0AAACDsl7gLuiv2PQEUNAuqQUAAAA%3D

    This involves compressing the input value using gzip, encoding the compressed value using base64, and using the resulting string as a URL parameter [2].

  2. Verify Configuration: Ensure that all environment variables in your docker-compose.yaml file are correctly set with your server's addresses. Misconfigurations in these URLs can lead to access issues [3].

  3. Firewall and Network Settings: Make sure that firewall ports are configured correctly and that your private Dify instance has internet access [4].

  4. Nginx Conflicts: Check if Nginx is already running on your system, as this can cause port conflicts. Use the following commands to troubleshoot:

    sudo systemctl status nginx
sudo systemctl stop nginx
docker compose up -d

    This should resolve any port conflicts between the system's Nginx and the Dify container's Nginx service [5].

These steps should help you resolve the "Cannot GET" error. If the issue persists, consider reviewing the Dify documentation for more detailed troubleshooting guidance.

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

@dosubot[bot] commented on GitHub (Mar 30, 2025): <!-- Answer --> I found a similar unsolved discussion that might be relevant to your issue: [Help](https://github.com/langgenius/dify/discussions/16313), which was last updated on March 20, 2025 <sup>[[1]](https://github.com/langgenius/dify/discussions/16313)</sup>. For the "Cannot GET" error in Dify's self-hosted deployment, here are some troubleshooting steps you can try: 1. **Check URL Structure**: Ensure that the URL structure for accessing the chatbot is correct. For Dify version 1.1.3, the expected URL structure is: ``` http://localhost/chatbot/{token}?name=H4sIAKUlmWYA%2FwWAIQ0AAACDsl7gLuiv2PQEUNAuqQUAAAA%3D ``` This involves compressing the input value using gzip, encoding the compressed value using base64, and using the resulting string as a URL parameter <sup>[[2]](https://github.com/langgenius/dify/issues/16565)</sup>. 2. **Verify Configuration**: Ensure that all environment variables in your `docker-compose.yaml` file are correctly set with your server's addresses. Misconfigurations in these URLs can lead to access issues <sup>[[3]](https://github.com/langgenius/dify/issues/16019)</sup>. 3. **Firewall and Network Settings**: Make sure that firewall ports are configured correctly and that your private Dify instance has internet access <sup>[[4]](https://github.com/langgenius/dify/issues/13501)</sup>. 4. **Nginx Conflicts**: Check if Nginx is already running on your system, as this can cause port conflicts. Use the following commands to troubleshoot: ```bash sudo systemctl status nginx sudo systemctl stop nginx docker compose up -d ``` This should resolve any port conflicts between the system's Nginx and the Dify container's Nginx service <sup>[[5]](https://github.com/langgenius/dify-docs/issues/421)</sup>. These steps should help you resolve the "Cannot GET" error. If the issue persists, consider reviewing the Dify documentation for more detailed troubleshooting guidance. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/81e347de-5bac-449d-8762-2eafa2a484db?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/81e347de-5bac-449d-8762-2eafa2a484db?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/81e347de-5bac-449d-8762-2eafa2a484db?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/81e347de-5bac-449d-8762-2eafa2a484db?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/81e347de-5bac-449d-8762-2eafa2a484db?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/81e347de-5bac-449d-8762-2eafa2a484db?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/81e347de-5bac-449d-8762-2eafa2a484db?feedback_type=other)</sup>
yindo commented 2026-02-21 19:07:03 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 30, 2025):

https://github.com/langgenius/dify/blob/0277a37fcad5ad86aeb239485c27fffd5cd90043/CONTRIBUTING.md#L23-L33

@crazywoola commented on GitHub (Mar 30, 2025): https://github.com/langgenius/dify/blob/0277a37fcad5ad86aeb239485c27fffd5cd90043/CONTRIBUTING.md#L23-L33
yindo commented 2026-02-21 19:07:03 -05:00
Author
Owner
Copy Link
Copy Source

@chenzaiming123 commented on GitHub (Mar 30, 2025):

Thanks! I've identified and resolved the issue. Changing the port to 8081 required adding the port number to the URL.

@chenzaiming123 commented on GitHub (Mar 30, 2025): Thanks! I've identified and resolved the issue. Changing the port to 8081 required adding the port number to the URL.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#12357
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?