langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-25 11:59:42 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The app icon fails to load. #21072

New Issue
Closed
opened 2026-02-21 20:10:33 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:10:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @shy20221121 on GitHub (Dec 15, 2025).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When returning to the studio page after spending some time on other pages, the app icon fails to load.

Image

✔️ Expected Behavior

App icon displays normally

❌ Actual Behavior

The app icon fails to load.

Originally created by @shy20221121 on GitHub (Dec 15, 2025). ### 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.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When returning to the studio page after spending some time on other pages, the app icon fails to load. <img width="100" height="102" alt="Image" src="https://github.com/user-attachments/assets/7cf13d3c-4036-4da6-be30-255479bdff75" /> ### ✔️ Expected Behavior App icon displays normally ### ❌ Actual Behavior The app icon fails to load.
yindo added the 🐞 bug label 2026-02-21 20:10:33 -05:00
yindo closed this issue 2026-02-21 20:10:33 -05:00
yindo commented 2026-02-21 20:10:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 15, 2025):

This issue is likely caused by a combination of frontend caching and static asset handling in Docker/Nginx. The app icon is rendered as an <img> using a URL provided by the backend; if that URL is cached or becomes invalid (for example, if it's a signed or short-lived URL), the icon will break when you return to the studio page. This is a known problem in self-hosted Docker setups, especially if static assets are aggressively cached or if there are misconfigurations in Nginx or Docker volume mounts.

A recent update fixed a bug in the app icon logic for image types, so upgrading to the latest Dify version is the most reliable solution for this issue cite.

If you need to troubleshoot on v1.11.1, try these steps:

  • Make sure you are using a freshly built Docker image and have not mounted any host volumes over the app’s static or chunk directories.
  • Clear your browser cache or do a hard refresh.
  • Check your Nginx config to ensure static assets are served with no-cache or a short max-age, and that path rewrites are correct if you use a subpath or reverse proxy cite.
  • If the problem persists, rebuild your Docker image from scratch and redeploy.

If you still see the broken icon, check the browser console and network tab for failed requests or 404s on the icon URL, and review your Docker and Nginx setup for static asset or path issues. Upgrading to a newer Dify version is strongly recommended, as many bugs related to icon path handling and static resource serving have been fixed in recent releases cite.

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 (Dec 15, 2025): <!-- Answer --> This issue is likely caused by a combination of frontend caching and static asset handling in Docker/Nginx. The app icon is rendered as an `<img>` using a URL provided by the backend; if that URL is cached or becomes invalid (for example, if it's a signed or short-lived URL), the icon will break when you return to the studio page. This is a known problem in self-hosted Docker setups, especially if static assets are aggressively cached or if there are misconfigurations in Nginx or Docker volume mounts. A recent update fixed a bug in the app icon logic for image types, so upgrading to the latest Dify version is the most reliable solution for this issue [cite](https://github.com/langgenius/dify/pull/27981). If you need to troubleshoot on v1.11.1, try these steps: - Make sure you are using a freshly built Docker image and have not mounted any host volumes over the app’s static or chunk directories. - Clear your browser cache or do a hard refresh. - Check your Nginx config to ensure static assets are served with `no-cache` or a short `max-age`, and that path rewrites are correct if you use a subpath or reverse proxy [cite](https://github.com/langgenius/dify/issues/23928). - If the problem persists, rebuild your Docker image from scratch and redeploy. If you still see the broken icon, check the browser console and network tab for failed requests or 404s on the icon URL, and review your Docker and Nginx setup for static asset or path issues. Upgrading to a newer Dify version is strongly recommended, as many bugs related to icon path handling and static resource serving have been fixed in recent releases [cite](https://github.com/langgenius/dify/issues/26332). <!-- 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/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?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%20issue%20is%20likely%20caused%20by%20a%20combination%20of%20frontend%20caching%20and%20static%20asset%20handling%20in%20Docker/Nginx.%20The%20app%20icon%20is%20rendered%20as%20an%20%60%3Cimg%3E%60%20using%20a%20URL%20provided%20by%20the%20backend%3B%20if%20that%20URL%20is%20cached%20or%20becomes%20invalid%20%28for%20example%2C%20if%20it%27s%20a%20signed%20or%20short-lived%20URL%29%2C%20the%20icon%20will%20break%20when%20you%20return%20to%20the%20studio%20page.%20This%20is%20a%20known%20problem%20in%20self-hosted%20Docker%20setups%2C%20especially%20if%20static%20assets%20are%20aggressively%20cached%20or%20if%20there%20are%20misconfigurations%20in%20Nginx%20or%20Docker%20volume%20mounts.%20%0A%0AA%20recent%20update%20fixed%20a%20bug%20in%20the%20app%20icon%20logic%20for%20image%20types%2C%20so%20upgrading%20to%20the%20latest%20Dify%20version%20is%20the%20most%20reliable%20solution%20for%20this%20issue%C2%A0%5Bcite%5D%28https%3A//github.com/langgenius/dify/pull/27981%29.%0A%0AIf%20you%20need%20to%20troubleshoot%20on%20v1.11.1%2C%20try%20these%20steps%3A%0A-%20Make%20sure%20you%20are%20using%20a%20freshly%20built%20Docker%20image%20and%20have%20not%20mounted%20any%20host%20volumes%20over%20the%20app%E2%80%99s%20static%20or%20chunk%20directories.%0A-%20Clear%20your%20browser%20cache%20or%20do%20a%20hard%20refresh.%0A-%20Check%20your%20Nginx%20config%20to%20ensure%20static%20assets%20are%20served%20with%20%60no-cache%60%20or%20a%20short%20%60max-age%60%2C%20and%20that%20path%20rewrites%20are%20correct%20if%20you%20use%20a%20subpath%20or%20reverse%20proxy%C2%A0%5Bcite%5D%28https%3A//github.com/langgenius/dify/issues/23928%29.%0A-%20If%20the%20problem%20persists%2C%20rebuild%20your%20Docker%20image%20from%20scratch%20and%20redeploy.%0A%0AIf%20you%20still%20see%20the%20broken%20icon%2C%20check%20the%20browser%20console%20and%20network%20tab%20for%20failed%20requests%20or%20404s%20on%20the%20icon%20URL%2C%20and%20review%20your%20Docker%20and%20Nginx%20setup%20for%20static%20asset%20or%20path%20issues.%20Upgrading%20to%20a%20newer%20Dify%20version%20is%20strongly%20recommended%2C%20as%20many%20bugs%20related%20to%20icon%20path%20handling%20and%20static%20resource%20serving%20have%20been%20fixed%20in%20recent%20releases%C2%A0%5Bcite%5D%28https%3A//github.com/langgenius/dify/issues/26332%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/29708)
yindo commented 2026-02-21 20:10:33 -05:00
Author
Owner
Copy Link
Copy Source

@shy20221121 commented on GitHub (Dec 15, 2025):

This issue is likely caused by a combination of frontend caching and static asset handling in Docker/Nginx. The app icon is rendered as an <img> using a URL provided by the backend; if that URL is cached or becomes invalid (for example, if it's a signed or short-lived URL), the icon will break when you return to the studio page. This is a known problem in self-hosted Docker setups, especially if static assets are aggressively cached or if there are misconfigurations in Nginx or Docker volume mounts.

A recent update fixed a bug in the app icon logic for image types, so upgrading to the latest Dify version is the most reliable solution for this issue cite.

If you need to troubleshoot on v1.11.1, try these steps:

  • Make sure you are using a freshly built Docker image and have not mounted any host volumes over the app’s static or chunk directories.
  • Clear your browser cache or do a hard refresh.
  • Check your Nginx config to ensure static assets are served with no-cache or a short max-age, and that path rewrites are correct if you use a subpath or reverse proxy cite.
  • If the problem persists, rebuild your Docker image from scratch and redeploy.

If you still see the broken icon, check the browser console and network tab for failed requests or 404s on the icon URL, and review your Docker and Nginx setup for static asset or path issues. Upgrading to a newer Dify version is strongly recommended, as many bugs related to icon path handling and static resource serving have been fixed in recent releases cite.

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

OKAY, THANKS

@shy20221121 commented on GitHub (Dec 15, 2025): > This issue is likely caused by a combination of frontend caching and static asset handling in Docker/Nginx. The app icon is rendered as an `<img>` using a URL provided by the backend; if that URL is cached or becomes invalid (for example, if it's a signed or short-lived URL), the icon will break when you return to the studio page. This is a known problem in self-hosted Docker setups, especially if static assets are aggressively cached or if there are misconfigurations in Nginx or Docker volume mounts. > > A recent update fixed a bug in the app icon logic for image types, so upgrading to the latest Dify version is the most reliable solution for this issue [cite](https://github.com/langgenius/dify/pull/27981). > > If you need to troubleshoot on v1.11.1, try these steps: > > * Make sure you are using a freshly built Docker image and have not mounted any host volumes over the app’s static or chunk directories. > * Clear your browser cache or do a hard refresh. > * Check your Nginx config to ensure static assets are served with `no-cache` or a short `max-age`, and that path rewrites are correct if you use a subpath or reverse proxy [cite](https://github.com/langgenius/dify/issues/23928). > * If the problem persists, rebuild your Docker image from scratch and redeploy. > > If you still see the broken icon, check the browser console and network tab for failed requests or 404s on the icon URL, and review your Docker and Nginx setup for static asset or path issues. Upgrading to a newer Dify version is strongly recommended, as many bugs related to icon path handling and static resource serving have been fixed in recent releases [cite](https://github.com/langgenius/dify/issues/26332). > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot)._ > > How did I do? [Good](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/39ed70dd-7181-4c39-a5c3-21b88b7bb81f?feedback_type=other) > > [![Chat with Dosu](https://camo.githubusercontent.com/7c571478962a6b8a5d47cac74b6824c75e4f6731bba52377e6007f9150462923/68747470733a2f2f646f73752e6465762f646f73752d636861742d62616467652e737667)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://camo.githubusercontent.com/bdf7dbded65ee585887f47e5fd6fa099ea0933088b4b03d02e83b4def50154d4/68747470733a2f2f646f73752e6465762f646f73752d696e2d637572736f722e737667)](https://cursor.com/link/prompt?text=This%20issue%20is%20likely%20caused%20by%20a%20combination%20of%20frontend%20caching%20and%20static%20asset%20handling%20in%20Docker/Nginx.%20The%20app%20icon%20is%20rendered%20as%20an%20%60%3Cimg%3E%60%20using%20a%20URL%20provided%20by%20the%20backend%3B%20if%20that%20URL%20is%20cached%20or%20becomes%20invalid%20%28for%20example%2C%20if%20it%27s%20a%20signed%20or%20short-lived%20URL%29%2C%20the%20icon%20will%20break%20when%20you%20return%20to%20the%20studio%20page.%20This%20is%20a%20known%20problem%20in%20self-hosted%20Docker%20setups%2C%20especially%20if%20static%20assets%20are%20aggressively%20cached%20or%20if%20there%20are%20misconfigurations%20in%20Nginx%20or%20Docker%20volume%20mounts.%20%0A%0AA%20recent%20update%20fixed%20a%20bug%20in%20the%20app%20icon%20logic%20for%20image%20types%2C%20so%20upgrading%20to%20the%20latest%20Dify%20version%20is%20the%20most%20reliable%20solution%20for%20this%20issue%C2%A0%5Bcite%5D%28https%3A//github.com/langgenius/dify/pull/27981%29.%0A%0AIf%20you%20need%20to%20troubleshoot%20on%20v1.11.1%2C%20try%20these%20steps%3A%0A-%20Make%20sure%20you%20are%20using%20a%20freshly%20built%20Docker%20image%20and%20have%20not%20mounted%20any%20host%20volumes%20over%20the%20app%E2%80%99s%20static%20or%20chunk%20directories.%0A-%20Clear%20your%20browser%20cache%20or%20do%20a%20hard%20refresh.%0A-%20Check%20your%20Nginx%20config%20to%20ensure%20static%20assets%20are%20served%20with%20%60no-cache%60%20or%20a%20short%20%60max-age%60%2C%20and%20that%20path%20rewrites%20are%20correct%20if%20you%20use%20a%20subpath%20or%20reverse%20proxy%C2%A0%5Bcite%5D%28https%3A//github.com/langgenius/dify/issues/23928%29.%0A-%20If%20the%20problem%20persists%2C%20rebuild%20your%20Docker%20image%20from%20scratch%20and%20redeploy.%0A%0AIf%20you%20still%20see%20the%20broken%20icon%2C%20check%20the%20browser%20console%20and%20network%20tab%20for%20failed%20requests%20or%20404s%20on%20the%20icon%20URL%2C%20and%20review%20your%20Docker%20and%20Nginx%20setup%20for%20static%20asset%20or%20path%20issues.%20Upgrading%20to%20a%20newer%20Dify%20version%20is%20strongly%20recommended%2C%20as%20many%20bugs%20related%20to%20icon%20path%20handling%20and%20static%20resource%20serving%20have%20been%20fixed%20in%20recent%20releases%C2%A0%5Bcite%5D%28https%3A//github.com/langgenius/dify/issues/26332%29.) [![Join Discord](https://camo.githubusercontent.com/7d2066700925db1e370d956834f9ea0e5bc92cecbe84963fbd2a363e45091b4e/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d)](https://go.dosu.dev/discord-bot) [![Share on X](https://camo.githubusercontent.com/a8bd7f3fcf3f5e3bd124eee9ae50ae2ac17b40971726665ac2121d48f9aee155/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f582d73686172652d626c61636b)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/29708) OKAY, THANKS
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#21072
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?