How to solve fetch failed error? #105

Activity

1. realgump commented on Mar 21, 2023

   

   realgump

   on Mar 21, 2023

   Last edited by realgump

   Author

   More actions

   And there are logs of server:

   chatgpt-clone-api-1     | model: chatgpt oldConvoId: null
   chatgpt-clone-api-1     | conversationId after old: a7307e5d-a432-456c-bd1f-e9df98e39ae6
   chatgpt-clone-api-1     | ask log {
   chatgpt-clone-api-1     |   model: 'chatgpt',
   chatgpt-clone-api-1     |   messageId: '77f48ea8-60c5-40b4-b4cd-c620f7257f31',
   chatgpt-clone-api-1     |   sender: 'User',
   chatgpt-clone-api-1     |   text: 'Explain quantum computing in simple terms',
   chatgpt-clone-api-1     |   parentMessageId: '00000000-0000-0000-0000-000000000000',
   chatgpt-clone-api-1     |   conversationId: 'a7307e5d-a432-456c-bd1f-e9df98e39ae6',
   chatgpt-clone-api-1     |   isCreatedByUser: true,
   chatgpt-clone-api-1     |   current: true,
   chatgpt-clone-api-1     |   chatGptLabel: null,
   chatgpt-clone-api-1     |   promptPrefix: null
   chatgpt-clone-api-1     | }
   chatgpt-clone-api-1     | TypeError: fetch failed
   chatgpt-clone-api-1     |     at Object.fetch (node:internal/deps/undici/undici:11457:11)
   chatgpt-clone-api-1     |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
   chatgpt-clone-api-1     |     at async create (file:///api/node_modules/@waylaidwanderer/fetch-event-source/lib/esm/fetch.js:52:34) {
   chatgpt-clone-api-1     |   cause: Error: connect ECONNREFUSED 127.0.0.1:7896
   chatgpt-clone-api-1     |       at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1532:16) {
   chatgpt-clone-api-1     |     errno: -111,
   chatgpt-clone-api-1     |     code: 'ECONNREFUSED',
   chatgpt-clone-api-1     |     syscall: 'connect',
   chatgpt-clone-api-1     |     address: '127.0.0.1',
   chatgpt-clone-api-1     |     port: 7896
   chatgpt-clone-api-1     |   }
   chatgpt-clone-api-1     | }
   
2. LibreChat-AI

   locked and limited conversation to collaborators on Mar 21, 2023
3. danny-avila

   converted this issue into a discussion #106 on Mar 21, 2023