search

langgenius / webapp-conversation

MIT License
444 stars 832 forks source link

Has anyone encountered a GET/serviceWorker.js 404 issue? #83

Closed Jerryqjr closed 3 months ago

Jerryqjr commented 3 months ago

Problem description

When I call APIs on the public network, although the terminal still reports an error GET /serviceWorker.js 404 in 102ms, this project is usable. When I deployed Dify on the company's intranet and called the API, the terminal reported an error GET/serviceWorker. js 404 in 102ms and the browser displayed a 500 App is unavailable error.

Error displayed on the terminal

problem

Attempt to solve

When I deployed Dify on the company's intranet and called the API,I printed error messages. error response I shut down my proxy server and firewall, but it didn't work.

And I tried testing the '/v1/chat messages' and' v1/conversion 'interfaces in Apifox and everything went smoothly, but when it came to the browser, it showed a 500 App is unavailable error.

There was no error message on the console. I checked the network option and found that the responses for all four interfaces were empty data.

network

Can anyone who has encountered this problem help me?I don't know how to fix it.

Local environment configuration

Node.js: 20.9.0 OS: Windows_NT x64 10.0.19045

Jerryqjr commented 3 months ago

This issue has been resolved, I have modified my proxy configuration

dxtbrave commented 3 months ago

This issue has been resolved, I have modified my proxy configuration Hello, may I ask how it was adjusted? I am currently facing this issue as well.

Jerryqjr commented 3 months ago

This issue has been resolved, I have modified my proxy configuration Hello, may I ask how it was adjusted? I am currently facing this issue as well.

For the GET/serviceWorker.js 404 issue, it is because my previous project ChatGPT-Next-Web cached serviceWorker.js in the browser and only needed to clean up local storage to solve it.

For the issue of 500 App is unavailable, I changed my proxy to direct connection and turned on the switch to allow LAN to solve it.

proxy