dify icon indicating copy to clipboard operation
dify copied to clipboard

Application error: a client-side exception has occurred (see the browser console for more information).

Open gene-coder opened this issue 1 year ago • 10 comments

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

v1.0.1(last version)

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

my step

I install dify in a self hosted(without internet), the step is

  • I install docker in my computer (use vmware workstation, centos 7 ), run "docker-compuse ..." to install dify,and dify is ok,
  • then run " docker sava -o dify.tar ...." to save the image, copy the dify.tar to a self hosted which without internet
  • run " docker load -i dify.tar" , then run "docker-compuse ..." to build then container.
  • 9 container is runing , when i open the web and create app , oops,the website show wrong.

what i want

Is any mistake in my step ?

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

gene-coder avatar Mar 11 '25 12:03 gene-coder

Hey there, @gene-coder! I'm here to help you with any bugs, questions, or contributions you have regarding Dify. Let's work together to solve this issue!

I found a similar open issue discussing client-side exceptions in a self-hosted environment. The suggested solution involves several troubleshooting steps:

  1. Check JavaScript File Integrity: Ensure all JavaScript files are correctly loaded. Verify that all necessary files were included during the image export and import process.

  2. Verify Network Configuration: Ensure that all internal network configurations are correct and that there are no restrictions preventing the application from accessing required resources.

  3. Inspect Build and Deployment Process: Ensure the build process for your application completed successfully without errors. Rebuild the application if necessary and check for any build-time warnings or errors.

  4. Check for Missing Dependencies: Make sure all dependencies are correctly installed and available in your Docker environment.

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

  6. Update Environment Variables: Double-check your environment variables to ensure they are correctly set, especially if they affect file paths or network configurations.

If these steps do not resolve the issue, consider rebuilding the Docker image and redeploying the application to ensure all components are correctly configured and up-to-date [[id=bc8ca]].

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] avatar Mar 11 '25 12:03 dosubot[bot]

please provide the logs in the web console.

crazywoola avatar Mar 11 '25 12:03 crazywoola

hook.js:608 TypeError: Cannot read properties of undefined (reading 'enabled') at 1340-5469e638ddbb6dad.js:1:1770690 at 1340-5469e638ddbb6dad.js:1:1771027 at rE (92df3e12-2414dde15c3f3d5d.js:1:40345) at l$ (92df3e12-2414dde15c3f3d5d.js:1:59320) at lU (92df3e12-2414dde15c3f3d5d.js:1:58165) at lI (92df3e12-2414dde15c3f3d5d.js:1:57770) at iZ (92df3e12-2414dde15c3f3d5d.js:1:121848) at ia (92df3e12-2414dde15c3f3d5d.js:1:95166) at 92df3e12-2414dde15c3f3d5d.js:1:94988 at il (92df3e12-2414dde15c3f3d5d.js:1:94995) at oJ (92df3e12-2414dde15c3f3d5d.js:1:92351) at nb (92df3e12-2414dde15c3f3d5d.js:1:26837) at 92df3e12-2414dde15c3f3d5d.js:1:108301 at is (92df3e12-2414dde15c3f3d5d.js:1:108309) at o1 (92df3e12-2414dde15c3f3d5d.js:1:93001) at oZ (92df3e12-2414dde15c3f3d5d.js:1:92156) at MessagePort.T (8597-3349f9d5ea3c44e6.js:1:84286)

at L && i.vision.enabled && (null === (e = i.vision.configs) || void 0 === e ? void 0 : e.variable_selector)) {

lisen-ai avatar Mar 12 '25 01:03 lisen-ai

Temporary fix: Manually export DSL, edit the yaml file and add vision: enabled: false under - data: of the corresponding node (in my case it was the question-classifier). Re-import DLS into a new app.

lisen-ai avatar Mar 12 '25 01:03 lisen-ai

I have the same problem too. When can it get fixed.

liujiawei9 avatar Mar 14 '25 07:03 liujiawei9

i have the same problem dify version is 0.15.3

SuperZhanggy avatar Mar 14 '25 08:03 SuperZhanggy

Image This problem occurs after importing the intent recognition customer service template in the exploration module, which is 100% reproduced. There is no problem in the 0.15.3 version, and it will appear on version 1.0.0 and 1.0.1.

liujiawei9 avatar Mar 17 '25 08:03 liujiawei9

I am having the same problem, but it occurred when I added Langfuse to the app monitoring. dify version is 1.01.

camucamulemon7 avatar Mar 17 '25 14:03 camucamulemon7

I am having the same problem, but it occurred when I added Langfuse to the app monitoring. dify version is 1.01.

I have same issue with this. Workflow contains only start, llm, end but link to langfuse, monitoring page shows same issue.

ChangooLee avatar Mar 18 '25 09:03 ChangooLee

In version 0.15.3, the customer support chatbox component encounters this issue when opened. Clearing the cache resolves the problem.

stoplyy avatar Mar 20 '25 10:03 stoplyy