Unexpected Application Error!

fetch failed

TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /var/www/insailing-frontend/node_modules/react-router/dist/development/index.js:3543:19
    at async callLoaderOrAction (/var/www/insailing-frontend/node_modules/react-router/dist/development/index.js:3593:16)
    at async Promise.all (index 0)
    at async defaultDataStrategy (/var/www/insailing-frontend/node_modules/react-router/dist/development/index.js:3471:17)
    at async callDataStrategyImpl (/var/www/insailing-frontend/node_modules/react-router/dist/development/index.js:3503:17)
    at async callDataStrategy (/var/www/insailing-frontend/node_modules/react-router/dist/development/index.js:3023:19)
    at async loadRouteData (/var/www/insailing-frontend/node_modules/react-router/dist/development/index.js:2990:19)
    at async queryImpl (/var/www/insailing-frontend/node_modules/react-router/dist/development/index.js:2839:20)
    at async query (/var/www/insailing-frontend/node_modules/react-router/dist/development/index.js:2760:18)
    at async getRouterAndContext (file:///var/www/insailing-frontend/build-server/AppSSR.js:69637:19)
    at async default (file:///var/www/insailing-frontend/server/middleware/renderer.js:79:41)

💿 Hey developer 👋

You can provide a way better UX than this when your app throws errors by providing your own ErrorBoundary or errorElement prop on your route.