langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The URL of run button did not include custom port when we deploy Dify with custom port #16211

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

Originally created by @crushonme on GitHub (Aug 17, 2025).

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

1.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Deploy Dify with custom port, for my environment, I used 8080 instead of 80.
  2. Setup a workflow and publish it.
  3. Click run button and we will see "404 Not Found" since there is no port after the url.

✔️ Expected Behavior

we expect there should be a custom port in the hyper link of run button.

❌ Actual Behavior

there is no custom port and we see "404 Not Found"

Originally created by @crushonme on GitHub (Aug 17, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Deploy Dify with custom port, for my environment, I used 8080 instead of 80. 2. Setup a workflow and publish it. 3. Click run button and we will see "404 Not Found" since there is no port after the url. ### ✔️ Expected Behavior we expect there should be a custom port in the hyper link of run button. ### ❌ Actual Behavior there is no custom port and we see "404 Not Found"
yindo added the 🌚 invalid label 2026-02-21 19:25:06 -05:00
yindo closed this issue 2026-02-21 19:25:06 -05:00
yindo commented 2026-02-21 19:25:07 -05:00
Author
Owner
Copy Link
Copy Source

@crushonme commented on GitHub (Aug 17, 2025):

In code of https://github.com/langgenius/dify/blob/0a9af4519462e78548142e689f2a6998ea63687e/web/app/components/app/app-publisher/index.tsx#L95, we did not add custom port.

  const { app_base_url: appBaseURL = '', access_token: accessToken = '' } = appDetail?.site ?? {}
  const appMode = (appDetail?.mode !== 'completion' && appDetail?.mode !== 'workflow') ? 'chat' : appDetail.mode
  const appURL = `${appBaseURL}${basePath}/${appMode}/${accessToken}`
@crushonme commented on GitHub (Aug 17, 2025): In code of https://github.com/langgenius/dify/blob/0a9af4519462e78548142e689f2a6998ea63687e/web/app/components/app/app-publisher/index.tsx#L95, we did not add custom port. ``` const { app_base_url: appBaseURL = '', access_token: accessToken = '' } = appDetail?.site ?? {} const appMode = (appDetail?.mode !== 'completion' && appDetail?.mode !== 'workflow') ? 'chat' : appDetail.mode const appURL = `${appBaseURL}${basePath}/${appMode}/${accessToken}` ```
yindo commented 2026-02-21 19:25:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 17, 2025):

Please read the document. https://docs.dify.ai/en/introduction

@crazywoola commented on GitHub (Aug 17, 2025): Please read the document. https://docs.dify.ai/en/introduction
yindo commented 2026-02-21 19:25:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 17, 2025):

https://github.com/langgenius/dify/blob/462ba8f41667154f840bf939227b5f89a2f1d901/docker/.env.example#L1-L53

@crazywoola commented on GitHub (Aug 17, 2025): https://github.com/langgenius/dify/blob/462ba8f41667154f840bf939227b5f89a2f1d901/docker/.env.example#L1-L53
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 🌚 invalid
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#16211
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?