The installed tool cannot load the icon
Self Checks
- [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
- [x] I have searched for existing issues search for existing issues, including closed ones.
- [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
- [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
- [x] Please do not modify this template :) and fill in all the required fields.
Dify version
1.0.0-beta.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Expected Behavior
The icon address was loaded from local 127.0.0.1, while my service is installed on the server
❌ Actual Behavior
http://localhost:5001/console/api/workspaces/current/plugin/icon?tenant_id=44d3edac-00cc-4171-bb4f-91c6adf6bd51&filename=1c5871163478957bac64c3fe33d72d003f767497d921c74b742aad27a8344a74.svg
Hey there, @caicongyang! 👋 I'm here to help you with any bugs, questions, or contributions you might have for the project. Let's squash those bugs together!
To resolve the issue of icons not loading and resulting in "ERR_CONNECTION_REFUSED" errors, ensure that the base URL for resource requests is correctly configured. In a self-hosted Dify environment, the NEXT_PUBLIC_PUBLIC_API_PREFIX environment variable should be set to the base URL of the Web App. This is crucial if the web app domain differs from the console or API domain. For example, it should be set to http://your-server-address:5001/api instead of http://localhost:5001/api [1].
Additionally, verify that the server is correctly configured to accept connections on the specified port (5001 in this case) and that there are no firewall rules blocking these requests. Ensure that the server address in your .env file is set to the correct external address where your Dify instance is hosted, replacing localhost with your actual server address [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
I also get the same error on my server
I have also encountered this problem. When adding a tool, the icon displays 404. Is there any way to solve it?