Publishing not working (self-hosted) #21933

Open
opened 2026-02-21 20:14:54 -05:00 by yindo · 5 comments
Owner

Originally created by @kylhuk on GitHub (Jan 27, 2026).

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.11.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Import attached DSL
  2. Press publish

GitLab Agent clean.yml

✔️ Expected Behavior

This should publish the application.

Actual Behavior

Nothing happens.

  • No console output
  • No network requests
  • No logs in docker
Originally created by @kylhuk on GitHub (Jan 27, 2026). ### 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.11.4 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Import attached DSL 2. Press publish [GitLab Agent clean.yml](https://github.com/user-attachments/files/24883211/GitLab.Agent.clean.yml) ### ✔️ Expected Behavior This should publish the application. ### ❌ Actual Behavior Nothing happens. - No console output - No network requests - No logs in docker
yindo added the 🐞 bug label 2026-02-21 20:14:54 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jan 27, 2026):

When publishing does nothing (no logs, no network activity), it usually means the backend publish endpoint isn't being called or is blocked before it can log anything. In self-hosted Docker setups, this can happen if required ports (like 5001) aren't exposed in your docker-compose.yaml, or if environment variables such as FILES_URL are missing or misconfigured. Make sure your Docker config exposes port 5001 and that FILES_URL is set to something like http://api:5001 for Docker Compose deployments. Restart your containers after making changes. Also, set LOG_LEVEL=DEBUG and (optionally) LOG_FILE in your .env to get more detailed logs, then check all container logs after reproducing the issue. If the publish button doesn't trigger any network request in your browser's dev tools, the problem may be in the frontend or a network/proxy misconfiguration blocking the API call before it reaches the backend. These silent failures are a known issue in self-hosted environments if the setup isn't complete or if dependencies are missing or not installed in the right place. For more details and troubleshooting steps, see this relevant thread.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 27, 2026): <!-- Answer --> When publishing does nothing (no logs, no network activity), it usually means the backend publish endpoint isn't being called or is blocked before it can log anything. In self-hosted Docker setups, this can happen if required ports (like 5001) aren't exposed in your `docker-compose.yaml`, or if environment variables such as `FILES_URL` are missing or misconfigured. Make sure your Docker config exposes port 5001 and that `FILES_URL` is set to something like `http://api:5001` for Docker Compose deployments. Restart your containers after making changes. Also, set `LOG_LEVEL=DEBUG` and (optionally) `LOG_FILE` in your `.env` to get more detailed logs, then check all container logs after reproducing the issue. If the publish button doesn't trigger any network request in your browser's dev tools, the problem may be in the frontend or a network/proxy misconfiguration blocking the API call before it reaches the backend. These silent failures are a known issue in self-hosted environments if the setup isn't complete or if dependencies are missing or not installed in the right place. For more details and troubleshooting steps, see [this relevant thread](https://github.com/langgenius/dify-official-plugins/issues/1816). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/6b44f9b1-5751-4c09-aa1c-fe7e28d5051b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6b44f9b1-5751-4c09-aa1c-fe7e28d5051b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6b44f9b1-5751-4c09-aa1c-fe7e28d5051b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6b44f9b1-5751-4c09-aa1c-fe7e28d5051b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6b44f9b1-5751-4c09-aa1c-fe7e28d5051b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6b44f9b1-5751-4c09-aa1c-fe7e28d5051b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6b44f9b1-5751-4c09-aa1c-fe7e28d5051b?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=When%20publishing%20does%20nothing%20%28no%20logs%2C%20no%20network%20activity%29%2C%20it%20usually%20means%20the%20backend%20publish%20endpoint%20isn%27t%20being%20called%20or%20is%20blocked%20before%20it%20can%20log%20anything.%20In%20self-hosted%20Docker%20setups%2C%20this%20can%20happen%20if%20required%20ports%20%28like%205001%29%20aren%27t%20exposed%20in%20your%20%60docker-compose.yaml%60%2C%20or%20if%20environment%20variables%20such%20as%20%60FILES_URL%60%20are%20missing%20or%20misconfigured.%20Make%20sure%20your%20Docker%20config%20exposes%20port%205001%20and%20that%20%60FILES_URL%60%20is%20set%20to%20something%20like%20%60http%3A//api%3A5001%60%20for%20Docker%20Compose%20deployments.%20Restart%20your%20containers%20after%20making%20changes.%20Also%2C%20set%20%60LOG_LEVEL%3DDEBUG%60%20and%20%28optionally%29%20%60LOG_FILE%60%20in%20your%20%60.env%60%20to%20get%20more%20detailed%20logs%2C%20then%20check%20all%20container%20logs%20after%20reproducing%20the%20issue.%20If%20the%20publish%20button%20doesn%27t%20trigger%20any%20network%20request%20in%20your%20browser%27s%20dev%20tools%2C%20the%20problem%20may%20be%20in%20the%20frontend%20or%20a%20network/proxy%20misconfiguration%20blocking%20the%20API%20call%20before%20it%20reaches%20the%20backend.%20These%20silent%20failures%20are%20a%20known%20issue%20in%20self-hosted%20environments%20if%20the%20setup%20isn%27t%20complete%20or%20if%20dependencies%20are%20missing%20or%20not%20installed%20in%20the%20right%20place.%20For%20more%20details%20and%20troubleshooting%20steps%2C%20see%20%5Bthis%20relevant%20thread%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1816%29.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31618)
Author
Owner

@kylhuk commented on GitHub (Jan 27, 2026):

@dosu

  1. port 5001 obviously has to be open, as I am able to access Dify
  2. increased log level does not do anything. As mentioned above, there is no request happening. The issue has to be on the client side
  3. setting FILES_URL=http://localhost:5001 and INTERNAL_FILES_URL=http://api:5001 did not resolve the issue.

Additional info:
Tested 3 different browsers: Waterfox, Safari, Chrome.

@kylhuk commented on GitHub (Jan 27, 2026): @dosu 1. port 5001 obviously has to be open, as I am able to access Dify 2. increased log level does not do anything. As mentioned above, there is no request happening. The issue has to be on the client side 3. setting `FILES_URL=http://localhost:5001` and `INTERNAL_FILES_URL=http://api:5001` did not resolve the issue. Additional info: Tested 3 different browsers: Waterfox, Safari, Chrome.
Author
Owner

@dosubot[bot] commented on GitHub (Jan 27, 2026):

Since no network request is triggered when you press publish, the most likely cause is frontend validation blocking the action before it reaches the backend. In Dify, the publish button will do nothing if there are unresolved checklist items, missing required nodes (like a start node), or if the workflow is misconfigured. This is enforced in the frontend and will show a toast error notification, but no network request or backend log will appear if validation fails source.

Please check for any error messages or warnings in the Dify UI right after pressing publish, and open your browser’s developer console to look for errors. Also, review the workflow checklist panel for unresolved items or warnings after importing your DSL—these must be resolved before publishing will work. If you see any errors or warnings, or if the checklist shows issues, resolving them should enable the publish action to proceed.

If you don’t see any UI feedback, try testing with a minimal or known-good DSL to rule out file-specific issues. If the problem persists, export the workflow as JSON and inspect it for missing required fields or share it for further analysis.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 27, 2026): <!-- Answer --> Since no network request is triggered when you press publish, the most likely cause is frontend validation blocking the action before it reaches the backend. In Dify, the publish button will do nothing if there are unresolved checklist items, missing required nodes (like a start node), or if the workflow is misconfigured. This is enforced in the frontend and will show a toast error notification, but no network request or backend log will appear if validation fails [source](https://github.com/langgenius/dify/pull/24104). Please check for any error messages or warnings in the Dify UI right after pressing publish, and open your browser’s developer console to look for errors. Also, review the workflow checklist panel for unresolved items or warnings after importing your DSL—these must be resolved before publishing will work. If you see any errors or warnings, or if the checklist shows issues, resolving them should enable the publish action to proceed. If you don’t see any UI feedback, try testing with a minimal or known-good DSL to rule out file-specific issues. If the problem persists, export the workflow as JSON and inspect it for missing required fields or share it for further analysis. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/af915daf-9f5a-4940-90ee-36f31492b870?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/af915daf-9f5a-4940-90ee-36f31492b870?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/af915daf-9f5a-4940-90ee-36f31492b870?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/af915daf-9f5a-4940-90ee-36f31492b870?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/af915daf-9f5a-4940-90ee-36f31492b870?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/af915daf-9f5a-4940-90ee-36f31492b870?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/af915daf-9f5a-4940-90ee-36f31492b870?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Since%20no%20network%20request%20is%20triggered%20when%20you%20press%20publish%2C%20the%20most%20likely%20cause%20is%20frontend%20validation%20blocking%20the%20action%20before%20it%20reaches%20the%20backend.%20In%20Dify%2C%20the%20publish%20button%20will%20do%20nothing%20if%20there%20are%20unresolved%20checklist%20items%2C%20missing%20required%20nodes%20%28like%20a%20start%20node%29%2C%20or%20if%20the%20workflow%20is%20misconfigured.%20This%20is%20enforced%20in%20the%20frontend%20and%20will%20show%20a%20toast%20error%20notification%2C%20but%20no%20network%20request%20or%20backend%20log%20will%20appear%20if%20validation%20fails%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/pull/24104%29.%0A%0APlease%20check%20for%20any%20error%20messages%20or%20warnings%20in%20the%20Dify%20UI%20right%20after%20pressing%20publish%2C%20and%20open%20your%20browser%E2%80%99s%20developer%20console%20to%20look%20for%20errors.%20Also%2C%20review%20the%20workflow%20checklist%20panel%20for%20unresolved%20items%20or%20warnings%20after%20importing%20your%20DSL%E2%80%94these%20must%20be%20resolved%20before%20publishing%20will%20work.%20If%20you%20see%20any%20errors%20or%20warnings%2C%20or%20if%20the%20checklist%20shows%20issues%2C%20resolving%20them%20should%20enable%20the%20publish%20action%20to%20proceed.%0A%0AIf%20you%20don%E2%80%99t%20see%20any%20UI%20feedback%2C%20try%20testing%20with%20a%20minimal%20or%20known-good%20DSL%20to%20rule%20out%20file-specific%20issues.%20If%20the%20problem%20persists%2C%20export%20the%20workflow%20as%20JSON%20and%20inspect%20it%20for%20missing%20required%20fields%20or%20share%20it%20for%20further%20analysis.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31618)
Author
Owner

@kylhuk commented on GitHub (Jan 27, 2026):

@dosu If I remove 99% of the components, I can publish. There are no errors visible and everything works. Also the test run works smoothly. This smells like a real bug.

@kylhuk commented on GitHub (Jan 27, 2026): @dosu If I remove 99% of the components, I can publish. There are no errors visible and everything works. Also the test run works smoothly. This smells like a real bug.
Author
Owner

@dosubot[bot] commented on GitHub (Jan 27, 2026):

This does match a known issue: Dify's frontend validation can silently block publishing if the workflow is too complex, has disconnected nodes, or exceeds certain limits—even if test runs work and no errors are shown in the UI. The publish button may be disabled or unresponsive if validation fails upstream, but without clear feedback or network activity, especially for large workflows or edge cases in the checklist logic (details, validation code).

To help pinpoint the cause, please check your browser’s developer console for any errors or warnings when you try to publish the full workflow. If possible, share the problematic DSL (or a reduced version that still triggers the bug). Comparing the minimal working DSL to the failing one may reveal differences like disconnected nodes, unusual constructs, or exceeding the tree depth limit.

If the workflow is within normal limits and you see no UI feedback or console errors, this is likely a frontend bug. Sharing the DSL and any console output will help maintainers reproduce and fix the issue.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 27, 2026): <!-- Answer --> This does match a known issue: Dify's frontend validation can silently block publishing if the workflow is too complex, has disconnected nodes, or exceeds certain limits—even if test runs work and no errors are shown in the UI. The publish button may be disabled or unresponsive if validation fails upstream, but without clear feedback or network activity, especially for large workflows or edge cases in the checklist logic ([details](https://github.com/langgenius/dify/discussions/28448), [validation code](https://github.com/langgenius/dify/blob/3d414678e336ed4ab4e071c197c69d90691ca3ac/web/app/components/workflow/hooks/use-checklist.ts#L87-L427)). To help pinpoint the cause, please check your browser’s developer console for any errors or warnings when you try to publish the full workflow. If possible, share the problematic DSL (or a reduced version that still triggers the bug). Comparing the minimal working DSL to the failing one may reveal differences like disconnected nodes, unusual constructs, or exceeding the tree depth limit. If the workflow is within normal limits and you see no UI feedback or console errors, this is likely a frontend bug. Sharing the DSL and any console output will help maintainers reproduce and fix the issue. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/71625efa-fadb-4028-9297-19e1402897a1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/71625efa-fadb-4028-9297-19e1402897a1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/71625efa-fadb-4028-9297-19e1402897a1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/71625efa-fadb-4028-9297-19e1402897a1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/71625efa-fadb-4028-9297-19e1402897a1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/71625efa-fadb-4028-9297-19e1402897a1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/71625efa-fadb-4028-9297-19e1402897a1?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20does%20match%20a%20known%20issue%3A%20Dify%27s%20frontend%20validation%20can%20silently%20block%20publishing%20if%20the%20workflow%20is%20too%20complex%2C%20has%20disconnected%20nodes%2C%20or%20exceeds%20certain%20limits%E2%80%94even%20if%20test%20runs%20work%20and%20no%20errors%20are%20shown%20in%20the%20UI.%20The%20publish%20button%20may%20be%20disabled%20or%20unresponsive%20if%20validation%20fails%20upstream%2C%20but%20without%20clear%20feedback%20or%20network%20activity%2C%20especially%20for%20large%20workflows%20or%20edge%20cases%20in%20the%20checklist%20logic%20%28%5Bdetails%5D%28https%3A//github.com/langgenius/dify/discussions/28448%29%2C%20%5Bvalidation%20code%5D%28https%3A//github.com/langgenius/dify/blob/3d414678e336ed4ab4e071c197c69d90691ca3ac/web/app/components/workflow/hooks/use-checklist.ts%23L87-L427%29%29.%0A%0ATo%20help%20pinpoint%20the%20cause%2C%20please%20check%20your%20browser%E2%80%99s%20developer%20console%20for%20any%20errors%20or%20warnings%20when%20you%20try%20to%20publish%20the%20full%20workflow.%20If%20possible%2C%20share%20the%20problematic%20DSL%20%28or%20a%20reduced%20version%20that%20still%20triggers%20the%20bug%29.%20Comparing%20the%20minimal%20working%20DSL%20to%20the%20failing%20one%20may%20reveal%20differences%20like%20disconnected%20nodes%2C%20unusual%20constructs%2C%20or%20exceeding%20the%20tree%20depth%20limit.%0A%0AIf%20the%20workflow%20is%20within%20normal%20limits%20and%20you%20see%20no%20UI%20feedback%20or%20console%20errors%2C%20this%20is%20likely%20a%20frontend%20bug.%20Sharing%20the%20DSL%20and%20any%20console%20output%20will%20help%20maintainers%20reproduce%20and%20fix%20the%20issue.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31618)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21933