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

Closed
opened 2026-02-16 10:15:54 -05:00 by yindo · 3 comments
Owner

Originally created by @Jerryqjr on GitHub (Jul 28, 2024).

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

Originally created by @Jerryqjr on GitHub (Jul 28, 2024). ## 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](https://github.com/user-attachments/assets/959bc3fa-36cb-43fb-bc2e-d52b1f97e18d) ## Attempt to solve When I deployed Dify on the company's intranet and called the API,I printed error messages. ![error](https://github.com/user-attachments/assets/e37b8f1e-34a6-4b04-b533-b6b065d9c53d) ![response](https://github.com/user-attachments/assets/88ba48bc-a7d7-4d24-a460-e11b97811707) 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](https://github.com/user-attachments/assets/ff23fa2a-0de6-4b0c-8375-8198d811adb0) 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
yindo closed this issue 2026-02-16 10:15:54 -05:00
Author
Owner

@Jerryqjr commented on GitHub (Jul 28, 2024):

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

@Jerryqjr commented on GitHub (Jul 28, 2024): This issue has been resolved, I have modified my proxy configuration
Author
Owner

@dxtbrave commented on GitHub (Aug 3, 2024):

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.

@dxtbrave commented on GitHub (Aug 3, 2024): > 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.
Author
Owner

@Jerryqjr commented on GitHub (Aug 5, 2024):

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

@Jerryqjr commented on GitHub (Aug 5, 2024): > > 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](https://github.com/user-attachments/assets/08845b16-e579-4696-9c3e-6c7dc61740bf)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/webapp-conversation#37