Issue Station
Sign In
Tools hereToolbox

dify - ✅(Solved) Fix missing port when "run" to view workflow page [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35285•Fetched 2026-04-16 07:06:39
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
1
Author
MinamiyamaMinamiyama
Participants
dosubot[bot]dosubot[bot]MinamiyamaMinamiyama
Timeline (top)
commented ×1cross-referenced ×1labeled ×1

Fix Action

Fixed

PR fix notes

PR #35275: fix(docker/nginx): preserve original Host header for upstream requests

Description (problem / solution / changelog)

Use $http_host instead of $host in the Docker nginx proxy template so the upstream app receives the original host value, including the externally accessed port when present. When APP_WEB_URL is not set, this fixes incorrect app_base_url generation in port-mapped Docker setups, such as accessing the app through localhost:3000 while nginx listens on port 80 inside the container.

Before

<img width="803" height="1239" alt="image" src="https://github.com/user-attachments/assets/cd5fca5f-a0db-482b-9d30-bb6554b8a517" /> <img width="1258" height="522" alt="image" src="https://github.com/user-attachments/assets/1202b980-8b89-4d72-9b32-82fffeb6b890" />

After

<img width="1314" height="1248" alt="image" src="https://github.com/user-attachments/assets/3544419e-c324-4f81-87b4-a5b8d499c178" /> <img width="1693" height="767" alt="image" src="https://github.com/user-attachments/assets/09714a93-e753-44ce-b52f-2a5deb24d19b" />

fix #35285

Changed files

  • docker/nginx/proxy.conf.template (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

all

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

<img width="1068" height="519" alt="Image" src="https://github.com/user-attachments/assets/d7cdcf8b-3f5f-4e90-a599-4fcc223bbe64" /> <img width="659" height="546" alt="Image" src="https://github.com/user-attachments/assets/caa084fa-7fd4-422d-ae91-6efad0392d13" />

✔️ Expected Behavior

view page with right port part same as dify url in browser

<img width="579" height="354" alt="Image" src="https://github.com/user-attachments/assets/74957ff0-cc36-4a2b-8383-d796ec5e68cd" />

❌ Actual Behavior

No response

extent analysis

TL;DR

The issue might be related to incorrect port configuration or Docker setup, causing the page to not respond as expected.

Guidance

  • Verify that the Docker container is running and exposed to the correct port, matching the one used in the Dify URL.
  • Check the Docker configuration files (e.g., docker-compose.yml) to ensure the port mapping is correct.
  • Confirm that there are no firewall or network issues blocking the connection to the Docker container.
  • Review the Dify documentation for any specific requirements or recommendations for self-hosted setups using Docker.

Notes

The provided images do not offer direct clues to the issue, but they might be relevant for understanding the expected behavior and setup. Without more detailed information about the Docker configuration and network setup, it's challenging to provide a precise solution.

Recommendation

Apply workaround: Verify and adjust the Docker configuration and port settings to ensure they match the expected behavior, as this seems to be the most likely cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#database connection#vector store#embedding generation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

dify - ✅(Solved) Fix missing port when "run" to view workflow page [1 pull requests, 1 comments, 2 participants]