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

After clicking publish, the custom port still doesn't appear. #12887

New Issue
Closed
opened 2026-02-21 19:09:32 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 19:09:32 -05:00
Owner
Copy Link
Copy Source

Originally created by @zismylove on GitHub (Apr 14, 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

i change .env config:
CONSOLE_API_URL
CONSOLE_WEB_URL
SERVICE_API_URL
APP_API_URL
APP_WEB_URL
,and change docker-compose.yml:
APP_WEB_URL
SERVICE_API_URL
,The issue still persists.

Image

Image

Image

✔️ Expected Behavior

I searched all afternoon and found 7 or 8 related issues and solutions, but even after restarting multiple times, the problem still couldn't be resolved.
Not sure what other areas need to be modified?

❌ Actual Behavior

No response

Originally created by @zismylove on GitHub (Apr 14, 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 i change .env config: CONSOLE_API_URL CONSOLE_WEB_URL SERVICE_API_URL APP_API_URL APP_WEB_URL ,and change docker-compose.yml: APP_WEB_URL SERVICE_API_URL ,The issue still persists. ![Image](https://github.com/user-attachments/assets/c1e56b7a-5644-4870-80c8-f83b7b78e52f) ![Image](https://github.com/user-attachments/assets/f03da3b8-f114-49df-9d91-c17bd662a739) ![Image](https://github.com/user-attachments/assets/f5d27beb-e0f9-40f0-ae03-e1c31740a6e9) ### ✔️ Expected Behavior I searched all afternoon and found 7 or 8 related issues and solutions, but even after restarting multiple times, the problem still couldn't be resolved. Not sure what other areas need to be modified? ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 19:09:32 -05:00
yindo closed this issue 2026-02-21 19:09:32 -05:00
yindo commented 2026-02-21 19:09:32 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 14, 2025):

For published application, you only need to change this line.

https://github.com/langgenius/dify/blob/5f8d20b5b2bb51f19547467167b18d9c0f6ffbb8/docker/.env.example#L33-L37

@crazywoola commented on GitHub (Apr 14, 2025): For published application, you only need to change this line. https://github.com/langgenius/dify/blob/5f8d20b5b2bb51f19547467167b18d9c0f6ffbb8/docker/.env.example#L33-L37
yindo commented 2026-02-21 19:09:32 -05:00
Author
Owner
Copy Link
Copy Source

@zismylove commented on GitHub (Apr 14, 2025):

For published application, you only need to change this line.

dify/docker/.env.example

Lines 33 to 37 in 5f8d20b

WebApp Url,

used to display WebAPP API Base Url to the front-end.

If empty, it is the same domain.

Example: https://app.dify.ai

APP_WEB_URL=

I came here to post the question because the changes I made didn't work.

@zismylove commented on GitHub (Apr 14, 2025): > For published application, you only need to change this line. > > [dify/docker/.env.example](https://github.com/langgenius/dify/blob/5f8d20b5b2bb51f19547467167b18d9c0f6ffbb8/docker/.env.example#L33-L37) > > Lines 33 to 37 in [5f8d20b](/langgenius/dify/commit/5f8d20b5b2bb51f19547467167b18d9c0f6ffbb8) > > # WebApp Url, > # used to display WebAPP API Base Url to the front-end. > # If empty, it is the same domain. > # Example: https://app.dify.ai > APP_WEB_URL= I came here to post the question because the changes I made didn't work.
yindo commented 2026-02-21 19:09:32 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 14, 2025):

I found a similar solved discussion regarding local deployment port issues. The solution involved changing the APP_WEB_URL in the .env file [1]. You can refer to the documentation for more details on configuring environment URLs for self-hosted deployment: Dify Environment Configuration.

Additionally, there is an open issue that suggests ensuring the service occupying the port is stopped or modifying the port mapping in the docker-compose.yaml file to map the port to another port [2]. You might want to check for any conditional logic in the docker-compose.yaml file that might override manual port changes.

If these solutions don't resolve your issue, consider using a script to automate the port mapping process, as described in the open issue [2].

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 (Apr 14, 2025): <!-- Answer --> I found a similar solved discussion regarding local deployment port issues. The solution involved changing the `APP_WEB_URL` in the `.env` file <sup>[[1]](https://github.com/langgenius/dify/discussions/13808)</sup>. You can refer to the documentation for more details on configuring environment URLs for self-hosted deployment: [Dify Environment Configuration](https://docs.dify.ai/getting-started/install-self-hosted/environments). Additionally, there is an open issue that suggests ensuring the service occupying the port is stopped or modifying the port mapping in the `docker-compose.yaml` file to map the port to another port <sup>[[2]](https://github.com/langgenius/dify/issues/7616)</sup>. You might want to check for any conditional logic in the `docker-compose.yaml` file that might override manual port changes. If these solutions don't resolve your issue, consider using a script to automate the port mapping process, as described in the open issue <sup>[[2]](https://github.com/langgenius/dify/issues/7616)</sup>. <!-- 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/ea140724-9d6b-47cb-a1e0-e8725d79f4f2?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ea140724-9d6b-47cb-a1e0-e8725d79f4f2?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ea140724-9d6b-47cb-a1e0-e8725d79f4f2?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ea140724-9d6b-47cb-a1e0-e8725d79f4f2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ea140724-9d6b-47cb-a1e0-e8725d79f4f2?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/ea140724-9d6b-47cb-a1e0-e8725d79f4f2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ea140724-9d6b-47cb-a1e0-e8725d79f4f2?feedback_type=other)</sup>
yindo commented 2026-02-21 19:09:32 -05:00
Author
Owner
Copy Link
Copy Source

@zismylove commented on GitHub (Apr 14, 2025):

Forget it, I'm done struggling. I shouldn't waste time on such a product.

@zismylove commented on GitHub (Apr 14, 2025): Forget it, I'm done struggling. I shouldn't waste time on such a product.
yindo commented 2026-02-21 19:09:32 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 14, 2025):

This is pretty straightforward to me, I am certain this should work, if it doesn't please provide more details.

Our greatest weakness lies in giving up. The most certain way to succeed is always to try just one more time.

@crazywoola commented on GitHub (Apr 14, 2025): This is pretty straightforward to me, I am certain this should work, if it doesn't please provide more details. > Our greatest weakness lies in giving up. The most certain way to succeed is always to try just one more time.
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 🤔 cant-reproduce
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#12887
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?