In most cases this is a proxy issue, not an OfferPotato crash.
Check the service directly:
curl --noproxy '*' http://127.0.0.1:6324/api/healthIf you get {"ok":true}, the server is healthy and your proxy path is the problem.
Fixes:
- add
127.0.0.1andlocalhosttoNO_PROXY - add your LAN IP to the browser or system proxy bypass list
- access the exact URLs printed by OfferPotato on startup
- Confirm the file was opened from the document panel
- Confirm the server still has access to the underlying local file
- Confirm the file watcher is not blocked by network filesystem permissions
- Run
npm run clean:data - rebuild the DB from the public-safe default config
- regenerate answers after the rebuild
- confirm
codexis installed and available inPATH - confirm websocket traffic is not intercepted by a proxy
- reload the page and click
重启会话
- confirm the new directory is placed under
sources/documents/orsources/question-banks/ - open Settings and check whether the auto-discovery counter has increased
- save and rebuild the index after adding new sources
- if you do not want a directory auto-detected, move it out of
sources/