[Bug] Cloud UI: Service Worker precaching fails with 404 after uploading ~300 .md files via API + prevents cloud.dify.ai from loading

[fulfly]

Self Checks

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

1. Is this request related to a challenge you're experiencing? Tell me about your story.

🐛 Summary

After uploading ~300 Markdown (.md) files to our dataset via the Dify Knowledge API, the Dify Cloud UI (https://cloud.dify.ai) stopped loading and shows:

"Application error: a client-side exception has occurred while loading cloud.dify.ai (see the browser console for more information)."

📍 Timeline

• ~22:00 Beijing Time
• Completed uploading ~300 MD files via our Python client
• Immediately after: could not load UI
• Tried multiple browsers, networks, cleared cache, invalid

🖥️ Actual Behavior

1. UI shows generic client-side exception:
   Application error: a client-side exception has occurred while loading cloud.dify.ai

2. Browser DevTools shows many 404 errors:
   Uncaught (in promise) bad-precaching-response ...
   {"url": "https://cloud.dify.ai/serwist/education/bg.png", "status": 404}
   {"url": "https://cloud.dify.ai/serwist/logo/logo-monochrome-white.svg", "status": 404}
   ...

3. Because of the 404 failures, the Service Worker never completes precaching and the UI fails to render.

📍 Steps to Reproduce

1. Upload a large number of Markdown files via the Dify API
2. Attempt to open https://cloud.dify.ai
3. Observe console errors (bad-precaching-response)

🔍 Expected Behavior

Static assets should be fetched from correct paths (no /serwist/ prefix) and precaching should succeed without 404 errors, so UI loads normally.

📓 Logs & Console Output

Application error: a client-side exception has occurred...
Uncaught (in promise) bad-precaching-response: ...
[404] /serwist/.../*.png/.svg

💡 Related GitHub Issue

There is a closed issue describing the Service Worker precache manifest problem:
#31677 :contentReference[oaicite:6]{index=6}

📎 Attachments

• Screenshot of the error page
• Console output (DevTools)

2. Additional context or comments

[f12 report.docx](https://github.com/user-attachments/files/25126384/f12.report.docx)

[dosubot[bot]]

Hi @fulfly! I'm Dosu and I’m helping the dify team.

This issue is caused by the Service Worker precache manifest referencing static assets with an incorrect /serwist/ prefix, which leads to 404 errors and prevents the UI from loading. This is a known problem that was previously tracked in issue #31677 and has now been fixed in a recent update. The fix (merged in PR #31770) normalizes the manifest URLs in the Service Worker, stripping the /serwist/ prefix so assets are fetched from the correct paths, and adds a rewrite rule to ensure proper routing of static assets during precaching. This should resolve the 404 errors and restore UI functionality once deployed to production. You can track the fix and its details here: PR #31770.

If you are still blocked while waiting for the fix to go live, you can try manually unregistering the Service Worker and clearing browser storage: open DevTools → Application tab → Service Workers → click "Unregister", then clear site data and reload the page. This may temporarily restore access if the issue is cached locally, but the root cause requires the deployment of the upstream fix.

To reply, just mention @dosu.

---

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