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

cannot access the plugin marketplace #8885

New Issue
Closed
opened 2026-02-21 18:28:23 -05:00 by yindo · 18 comments
yindo commented 2026-02-21 18:28:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @yuanzhiwei on GitHub (Mar 3, 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.0.0

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

The Linux server cannot access the plugin marketplace [https://marketplace.dify.ai/]. Did Dify officially impose server IP restrictions?

The server is provided by UCloud, with IP address 106.75.126.202.‌

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @yuanzhiwei on GitHub (Mar 3, 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.0.0 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce The Linux server cannot access the plugin marketplace [https://marketplace.dify.ai/]. Did Dify officially impose server IP restrictions? The server is provided by UCloud, with IP address 106.75.126.202.‌ ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:28:23 -05:00
yindo closed this issue 2026-02-21 18:28:23 -05:00
yindo commented 2026-02-21 18:28:23 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

@yuanzhiwei Hello! I'm here to help you with any bugs, questions, or contributions you may have.

The issue you're experiencing with accessing the Dify plugin marketplace in a self-hosted environment might be related to known issues such as DNS resolution problems or SSL connection errors. These issues can occur if access to marketplace.dify.ai is blocked by network restrictions like the Great Firewall (GFW) or if there are SSL configuration problems.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

  1. DNS and Network Configuration: Ensure that your DNS settings are correctly configured. If you're in a region with network restrictions, consider using a VPN to bypass these restrictions.

  2. SSL Configuration: Verify that your SSL certificates are correctly configured. Check the NGINX_SSL_CERT_FILENAME and NGINX_SSL_CERT_KEY_FILENAME in your Docker configuration to ensure they point to the correct files [1].

  3. Proxy Settings: If you're using a proxy, ensure that the HTTP_PROXY and HTTPS_PROXY environment variables are correctly set. Incorrect proxy settings can interfere with network connections [2].

  4. Version Update: If the issue persists, consider updating to the latest version of Dify, as updates often include bug fixes and improvements [3].

If these steps do not resolve the issue, further investigation into your network environment may be necessary.

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 (Mar 3, 2025): <!-- Greeting --> @yuanzhiwei Hello! I'm here to help you with any bugs, questions, or contributions you may have. <!-- Answer --> The issue you're experiencing with accessing the Dify plugin marketplace in a self-hosted environment might be related to known issues such as DNS resolution problems or SSL connection errors. These issues can occur if access to marketplace.dify.ai is blocked by network restrictions like the Great Firewall (GFW) or if there are SSL configuration problems. Here are some steps you can take to troubleshoot and potentially resolve the issue: 1. **DNS and Network Configuration**: Ensure that your DNS settings are correctly configured. If you're in a region with network restrictions, consider using a VPN to bypass these restrictions. 2. **SSL Configuration**: Verify that your SSL certificates are correctly configured. Check the `NGINX_SSL_CERT_FILENAME` and `NGINX_SSL_CERT_KEY_FILENAME` in your Docker configuration to ensure they point to the correct files <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. 3. **Proxy Settings**: If you're using a proxy, ensure that the `HTTP_PROXY` and `HTTPS_PROXY` environment variables are correctly set. Incorrect proxy settings can interfere with network connections <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/jp/learn-more/faq/install-faq.md)</sup>. 4. **Version Update**: If the issue persists, consider updating to the latest version of Dify, as updates often include bug fixes and improvements <sup>[[3]](https://github.com/langgenius/dify/issues/12617)</sup>. If these steps do not resolve the issue, further investigation into your network environment may be necessary. <!-- 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/80cf2413-3c5f-45e0-8e75-8fd0ba02ccbd?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/80cf2413-3c5f-45e0-8e75-8fd0ba02ccbd?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/80cf2413-3c5f-45e0-8e75-8fd0ba02ccbd?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/80cf2413-3c5f-45e0-8e75-8fd0ba02ccbd?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/80cf2413-3c5f-45e0-8e75-8fd0ba02ccbd?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/80cf2413-3c5f-45e0-8e75-8fd0ba02ccbd?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/80cf2413-3c5f-45e0-8e75-8fd0ba02ccbd?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:23 -05:00
Author
Owner
Copy Link
Copy Source

@yuanzhiwei commented on GitHub (Mar 3, 2025):

‌The Linux server has no network connectivity issues, but cannot access the plugin marketplace.‌‌

@yuanzhiwei commented on GitHub (Mar 3, 2025): ‌The Linux server has no network connectivity issues, but cannot access the plugin marketplace.‌‌
yindo commented 2026-02-21 18:28:23 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 3, 2025):

Afaik, there is no restrictions on this site https://marketplace.dify.ai/

@crazywoola commented on GitHub (Mar 3, 2025): Afaik, there is no restrictions on this site https://marketplace.dify.ai/
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@xuesd commented on GitHub (Mar 3, 2025):

Does the. env. local file exist in the web folder?

@xuesd commented on GitHub (Mar 3, 2025): Does the. env. local file exist in the web folder?
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@yuanzhiwei commented on GitHub (Mar 3, 2025):

Image
This is the feedback from server provider.‌

Image
The curl.

@yuanzhiwei commented on GitHub (Mar 3, 2025): ![Image](https://github.com/user-attachments/assets/f7a96202-d9d1-4100-8240-e492b8c5cb27) This is the feedback from server provider.‌ ![Image](https://github.com/user-attachments/assets/efc4c3e9-4238-4fff-a2be-66622b058efb) The curl.
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@yuanzhiwei commented on GitHub (Mar 3, 2025):

Does the. env. local file exist in the web folder?

The process hasn't reached this stage yet. When upgrading the backend to version 1.0.0, a plugin download was required, but the connection failed at this step ‌.

@yuanzhiwei commented on GitHub (Mar 3, 2025): > Does the. env. local file exist in the web folder? The process hasn't reached this stage yet. When upgrading the backend to version 1.0.0, a plugin download was required, but the connection failed at this step ‌.
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@YULIANGMAX commented on GitHub (Mar 3, 2025):

I have encountered the same problem with my server hosted on Aliyun, with the IP address 39.98.115.214. When attempting to ping marketplace.dify.ai from this server, it fails with a 100% packet loss. However, the domain marketplace.dify.ai resolves to the IP address 104.26.8.156.

Subsequently, when I tried to ping 104.26.8.156, I also experienced 100% packet loss. However, pinging adjacent IPs (such as 104.26.8.157) worked without any issues.

Additionally, I attempted the same tests from a server located in a different region, and was able to successfully ping marketplace.dify.ai.

Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed.

@YULIANGMAX commented on GitHub (Mar 3, 2025): I have encountered the same problem with my server hosted on Aliyun, with the IP address 39.98.115.214. When attempting to ping marketplace.dify.ai from this server, it fails with a 100% packet loss. However, the domain marketplace.dify.ai resolves to the IP address 104.26.8.156. Subsequently, when I tried to ping 104.26.8.156, I also experienced 100% packet loss. However, pinging adjacent IPs (such as 104.26.8.157) worked without any issues. Additionally, I attempted the same tests from a server located in a different region, and was able to successfully ping marketplace.dify.ai. Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed.
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@hope250 commented on GitHub (Mar 7, 2025):

Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed.

so sad :(

@hope250 commented on GitHub (Mar 7, 2025): > Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed. so sad :(
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@tianji2018 commented on GitHub (Mar 10, 2025):

我的解析到的是172.67.71.187，ip归属地是美国，访问不了

@tianji2018 commented on GitHub (Mar 10, 2025): 我的解析到的是172.67.71.187，ip归属地是美国，访问不了
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@tttpeng commented on GitHub (Mar 12, 2025):

Is there a method to configure a http proxy specifically for accessing marketplace.dify.ai, ensuring that this HTTP proxy does not interfere with other modules?

@tttpeng commented on GitHub (Mar 12, 2025): Is there a method to configure a http proxy specifically for accessing marketplace.dify.ai, ensuring that this HTTP proxy does not interfere with other modules?
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@Steven-Luo commented on GitHub (Mar 12, 2025):

试了一晚上，在docker/.env文件文件中配置这个代理可以解决问题，日志里面报警的是api/core/helper/ssrf_proxy.py 61行，大概推测出来需要这两个环境变量

Image

@Steven-Luo commented on GitHub (Mar 12, 2025): 试了一晚上，在docker/.env文件文件中配置这个代理可以解决问题，日志里面报警的是api/core/helper/ssrf_proxy.py 61行，大概推测出来需要这两个环境变量 ![Image](https://github.com/user-attachments/assets/fec7014c-06cc-4276-8e3a-d62591c7d7f3)
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@yuanzhiwei commented on GitHub (Mar 12, 2025):

试了一晚上，在docker/.env文件文件中配置这个代理可以解决问题，日志里面报警的是api/core/helper/ssrf_proxy.py 61行，大概推测出来需要这两个环境变量

Image

我也是这样挂个代理，先把插件下载下来，然后换回去启动的， 云厂商那边说这个域名限制了BGP线路IP的访问，但是官方没有回复限制的原因

@yuanzhiwei commented on GitHub (Mar 12, 2025): > 试了一晚上，在docker/.env文件文件中配置这个代理可以解决问题，日志里面报警的是api/core/helper/ssrf_proxy.py 61行，大概推测出来需要这两个环境变量 > > ![Image](https://github.com/user-attachments/assets/fec7014c-06cc-4276-8e3a-d62591c7d7f3) 我也是这样挂个代理，先把插件下载下来，然后换回去启动的， 云厂商那边说这个域名限制了BGP线路IP的访问，但是官方没有回复限制的原因
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@saaa302 commented on GitHub (Mar 20, 2025):

I have encountered the same problem with my server hosted on Aliyun, with the IP address 39.98.115.214. When attempting to ping marketplace.dify.ai from this server, it fails with a 100% packet loss. However, the domain marketplace.dify.ai resolves to the IP address 104.26.8.156.

Subsequently, when I tried to ping 104.26.8.156, I also experienced 100% packet loss. However, pinging adjacent IPs (such as 104.26.8.157) worked without any issues.

Additionally, I attempted the same tests from a server located in a different region, and was able to successfully ping marketplace.dify.ai.

Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed.

Has your problem been resolved? I'm currently facing the same issue on Aliyun

@saaa302 commented on GitHub (Mar 20, 2025): > I have encountered the same problem with my server hosted on Aliyun, with the IP address 39.98.115.214. When attempting to ping marketplace.dify.ai from this server, it fails with a 100% packet loss. However, the domain marketplace.dify.ai resolves to the IP address 104.26.8.156. > > Subsequently, when I tried to ping 104.26.8.156, I also experienced 100% packet loss. However, pinging adjacent IPs (such as 104.26.8.157) worked without any issues. > > Additionally, I attempted the same tests from a server located in a different region, and was able to successfully ping marketplace.dify.ai. > > Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed. Has your problem been resolved? I'm currently facing the same issue on Aliyun
yindo commented 2026-02-21 18:28:24 -05:00
Author
Owner
Copy Link
Copy Source

@tianji2018 commented on GitHub (Mar 20, 2025):

I have encountered the same problem with my server hosted on Aliyun, with the IP address 39.98.115.214. When attempting to ping marketplace.dify.ai from this server, it fails with a 100% packet loss. However, the domain marketplace.dify.ai resolves to the IP address 104.26.8.156.
Subsequently, when I tried to ping 104.26.8.156, I also experienced 100% packet loss. However, pinging adjacent IPs (such as 104.26.8.157) worked without any issues.
Additionally, I attempted the same tests from a server located in a different region, and was able to successfully ping marketplace.dify.ai.
Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed.

Has your problem been resolved? I'm currently facing the same issue on Aliyun

我测试着北京节点的好像不能访问，青岛节点可以

@tianji2018 commented on GitHub (Mar 20, 2025): > > I have encountered the same problem with my server hosted on Aliyun, with the IP address 39.98.115.214. When attempting to ping marketplace.dify.ai from this server, it fails with a 100% packet loss. However, the domain marketplace.dify.ai resolves to the IP address 104.26.8.156. > > Subsequently, when I tried to ping 104.26.8.156, I also experienced 100% packet loss. However, pinging adjacent IPs (such as 104.26.8.157) worked without any issues. > > Additionally, I attempted the same tests from a server located in a different region, and was able to successfully ping marketplace.dify.ai. > > Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed. > > Has your problem been resolved? I'm currently facing the same issue on Aliyun 我测试着北京节点的好像不能访问，青岛节点可以
yindo commented 2026-02-21 18:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@saaa302 commented on GitHub (Mar 20, 2025):

I have encountered the same problem with my server hosted on Aliyun, with the IP address 39.98.115.214. When attempting to ping marketplace.dify.ai from this server, it fails with a 100% packet loss. However, the domain marketplace.dify.ai resolves to the IP address 104.26.8.156.
Subsequently, when I tried to ping 104.26.8.156, I also experienced 100% packet loss. However, pinging adjacent IPs (such as 104.26.8.157) worked without any issues.
Additionally, I attempted the same tests from a server located in a different region, and was able to successfully ping marketplace.dify.ai.
Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed.

Has your problem been resolved? I'm currently facing the same issue on Aliyun

我测试着北京节点的好像不能访问，青岛节点可以

我的服务器是在：华北2（北京）

@saaa302 commented on GitHub (Mar 20, 2025): > > > I have encountered the same problem with my server hosted on Aliyun, with the IP address 39.98.115.214. When attempting to ping marketplace.dify.ai from this server, it fails with a 100% packet loss. However, the domain marketplace.dify.ai resolves to the IP address 104.26.8.156. > > > Subsequently, when I tried to ping 104.26.8.156, I also experienced 100% packet loss. However, pinging adjacent IPs (such as 104.26.8.157) worked without any issues. > > > Additionally, I attempted the same tests from a server located in a different region, and was able to successfully ping marketplace.dify.ai. > > > Due to this issue, I had to temporarily rollback to version 0.15.3 on the original server where upgrades are needed. > > > > > > Has your problem been resolved? I'm currently facing the same issue on Aliyun > > 我测试着北京节点的好像不能访问，青岛节点可以 我的服务器是在：华北2（北京）
yindo commented 2026-02-21 18:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@litaosmile commented on GitHub (Mar 20, 2025):

阿里云 华北ECS 云主机，遇到同样问题

@litaosmile commented on GitHub (Mar 20, 2025): 阿里云 华北ECS 云主机，遇到同样问题
yindo commented 2026-02-21 18:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@conglei1981 commented on GitHub (Mar 24, 2025):

个人电脑北京的也不能访问，所以dify是不让中国用么

@conglei1981 commented on GitHub (Mar 24, 2025): 个人电脑北京的也不能访问，所以dify是不让中国用么
yindo commented 2026-02-21 18:28:25 -05:00
Author
Owner
Copy Link
Copy Source

@kyler-bai commented on GitHub (Jan 22, 2026):

https://marketplace.dify.ai/
插件市场依旧打不开，如此重要的节点...，难以相信Dify的前景与未来

@kyler-bai commented on GitHub (Jan 22, 2026): https://marketplace.dify.ai/ 插件市场依旧打不开，如此重要的节点...，难以相信Dify的前景与未来
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
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#8885
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?