Cannot open new or existing application with old browser

[josh-zhang]

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

0.14.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

docker images pulled from dockerhub, deploy on the server with no Internet access, was working properly with version 0.11.1 and 0.11.2.

1. upgrade from 0.11.2 to 0.14.2 (and volume folder copied from 0.11.2 one)
2. docker compose up -d
3. logged in with old browser (e.g. Chorme v87)
4. click any existing app, and then got blank page with err msg "Application error ***". browser console got msg "loadingchunkfailed loading chunk 4046 failed"
5. OR, create new app, after finished in the popup window and click "create", then also got blank page with err msg "Application error ***". browser console got msg "loadingchunkfailed loading chunk 4046 failed"

SAME issue when upgrade 0.11.2 to 0.14.1

✔️ Expected Behavior

above function working properly

❌ Actual Behavior

1. click any existing app, and then got blank page with err msg "Application error ***", and the browser console got msg "loadingchunkfailed loading chunk 4046 failed"
2. OR, create new app, after finished in the popup window and click "create", then also got blank page with err msg "Application error ***", and the browser console got msg "loadingchunkfailed loading chunk 4046 failed"

[dosubot]

The "loadingchunkfailed" error you're encountering typically indicates an issue with loading JavaScript chunks in the web application. This can happen due to several reasons, especially after an upgrade. Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Clear Browser Cache: Sometimes, old cached files can cause issues after an upgrade. Clear your browser cache and try accessing the application again.

2. Check Network Configuration: Ensure that your server's network configuration allows access to all necessary resources. Since your server has no internet access, verify that all required assets are available locally.

3. Verify Docker Setup: Make sure that all Docker containers are running correctly. You can check the status of your containers using:

   docker ps

4. Inspect Docker Logs: Check the logs of your Docker containers for any errors or warnings that might provide more insight into the issue:

   docker logs <container_id>

5. Rebuild Frontend Assets: If you have access to the source code, try rebuilding the frontend assets. This can help resolve issues related to missing or corrupted chunks:

   cd web
   npm run build
   npm run start

6. Check for Missing Environment Variables: Ensure that your .env file is up-to-date with the latest configuration options required by version 0.14.2. Compare it with the .env.example file provided in the repository.

7. Review Upgrade Steps: Double-check that all steps for upgrading from version 0.11.2 to 0.14.2 were followed correctly, including any changes to environment variables or Docker configurations ^[1].

If these steps do not resolve the issue, consider rolling back to a previous version that was working and then attempt the upgrade again, ensuring all steps are followed precisely.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[josh-zhang]

error gone when client switched to newer version of Chrome (e.g. v131)...was using v87...