import app from old version dsl failed #13191

Closed
opened 2026-02-21 19:10:59 -05:00 by yindo · 2 comments
Owner

Originally created by @JustWeZero on GitHub (Apr 21, 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.2.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. import app from a dsl file in an offline environment.

✔️ Expected Behavior

import using a dsl file with no error.

Actual Behavior

I'm using dify in an offline environment. Yesterday I upgrade from 0.15.3 to 1.2.0, and when I import an app using a dsl file, I got an error: create app failed.
I have set environment variable: HOSTED_FETCH_APP_TEMPLATES_MODE: builtin.

Image

TrackBack:
Image
Image

Originally created by @JustWeZero on GitHub (Apr 21, 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.2.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. import app from a dsl file in an offline environment. ### ✔️ Expected Behavior import using a dsl file with no error. ### ❌ Actual Behavior I'm using dify in an offline environment. Yesterday I upgrade from 0.15.3 to 1.2.0, and when I import an app using a dsl file, I got an error: create app failed. I have set environment variable: HOSTED_FETCH_APP_TEMPLATES_MODE: builtin. ![Image](https://github.com/user-attachments/assets/9cabb6d4-39fd-4cf4-88fd-d56ac9ffc783) TrackBack: ![Image](https://github.com/user-attachments/assets/414f02ae-17c0-4486-8e5f-e6d6213de425) ![Image](https://github.com/user-attachments/assets/d4c210e1-44bd-47d6-b031-dbce6f6e5607)
yindo added the 🐞 bug label 2026-02-21 19:10:59 -05:00
yindo closed this issue 2026-02-21 19:10:59 -05:00
Author
Owner

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

Hello @JustWeZero! I'm Dosu, your friendly bot here to help you tackle bugs, answer questions, and guide you on your journey to becoming a contributor. I'm here while you wait for a human maintainer. Let's get started!

To resolve the "create app failed" error when importing an app from a DSL file in an offline environment after upgrading Dify from version 0.15.3 to 1.2.0, you need to address the issue related to the failure in resolving the hostname 'marketplace.dify.ai'. This problem has been fixed in pull request #18273. Upgrading to a version of Dify that includes this fix will resolve the error.

Additionally, you can modify the docker-compose.yaml file to set the MARKETPLACE_API_URL and MARKETPLACE_URL environment variables to point to a local or alternative URL that does not require internet access. This can help bypass the hostname resolution issue in offline environments.

Furthermore, adjust your .env file settings to better suit an offline environment by setting MARKETPLACE_ENABLED to false and using an internal pip mirror for dependencies. Add the following to your .env file:

CHECK_UPDATE_URL=http://127.0.0.1/
MARKETPLACE_ENABLED=false
MARKETPLACE_API_URL=https://marketplace.dify.ai
FORCE_VERIFYING_SIGNATURE=false
PIP_MIRROR_URL=[your internal pip mirror URL]

These changes will disable external update checks, disable the marketplace, and use your internal pip mirror for dependencies, which should help resolve DNS resolution failures and dependency installation errors in an offline environment [1].

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 21, 2025): <!-- Greeting --> Hello @JustWeZero! I'm [Dosu](https://dosu.dev), your friendly bot here to help you tackle bugs, answer questions, and guide you on your journey to becoming a contributor. I'm here while you wait for a human maintainer. Let's get started! <!-- Answer --> To resolve the "create app failed" error when importing an app from a DSL file in an offline environment after upgrading Dify from version 0.15.3 to 1.2.0, you need to address the issue related to the failure in resolving the hostname 'marketplace.dify.ai'. This problem has been fixed in pull request #18273. Upgrading to a version of Dify that includes this fix will resolve the error. Additionally, you can modify the `docker-compose.yaml` file to set the `MARKETPLACE_API_URL` and `MARKETPLACE_URL` environment variables to point to a local or alternative URL that does not require internet access. This can help bypass the hostname resolution issue in offline environments. Furthermore, adjust your `.env` file settings to better suit an offline environment by setting `MARKETPLACE_ENABLED` to `false` and using an internal pip mirror for dependencies. Add the following to your `.env` file: ``` CHECK_UPDATE_URL=http://127.0.0.1/ MARKETPLACE_ENABLED=false MARKETPLACE_API_URL=https://marketplace.dify.ai FORCE_VERIFYING_SIGNATURE=false PIP_MIRROR_URL=[your internal pip mirror URL] ``` These changes will disable external update checks, disable the marketplace, and use your internal pip mirror for dependencies, which should help resolve DNS resolution failures and dependency installation errors in an offline environment <sup>[[1]](https://github.com/langgenius/dify/issues/18318)</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/48ab1979-30fe-4ba8-bcd9-cbf494fa7666?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/48ab1979-30fe-4ba8-bcd9-cbf494fa7666?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/48ab1979-30fe-4ba8-bcd9-cbf494fa7666?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/48ab1979-30fe-4ba8-bcd9-cbf494fa7666?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/48ab1979-30fe-4ba8-bcd9-cbf494fa7666?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/48ab1979-30fe-4ba8-bcd9-cbf494fa7666?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/48ab1979-30fe-4ba8-bcd9-cbf494fa7666?feedback_type=other)</sup>
Author
Owner

@MrXionGe commented on GitHub (Aug 21, 2025):

In the .env file, change the value of the parameter to false.

MARKETPLACE_ENABLED=false

Self-hosted applications usually prohibit access to external networks. Therefore, you need to disable the application market.

Using the above solution, we migrated many agents from 0.15.8 to 1.7.2.

@MrXionGe commented on GitHub (Aug 21, 2025): In the .env file, change the value of the parameter to false. `MARKETPLACE_ENABLED=false` Self-hosted applications usually prohibit access to external networks. Therefore, you need to disable the application market. Using the above solution, we migrated many agents from 0.15.8 to 1.7.2.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#13191