My API's are not working

threathunter369 · November 11, 2024, 4:11am

Hi Guys,

I wonder if any of you also experience that your API’s are not working?

I have a newly spin up oTTODev on my Ubuntu Vm, I always get this error while stating to chat with oTTODev.

“There was an error processing your request”

even if i have my API,s included in .env file.

I have this errors on the console after my first chat:

The resource https://w-corp-staticblitz.com/fetch.worker.f565b097.js was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.Understand this warningAI
:5174/api/chat:1 
        
        
       Failed to load resource: the server responded with a status of 500 (Internal Server Error)Understand this errorAI
logger.ts:84 ERROR Chat Request failed

Error
headless:1 The resource https://w-corp-staticblitz.com/fetch.worker.f565b097.js was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.Understand this warningAI
blitz.f565b097.js:19 [Contextify] [WARNING] running source code in new context
(anonymous) @ blitz.f565b097.js:19Understand this warningAI
headless:1 The resource https://w-corp-staticblitz.com/fetch.worker.f565b097.js was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.Understand this warningAI
Chat.client.tsx:200 
        
        
       POST http://localhost:5174/api/chat 500 (Internal Server Error)
callChatApi @ ai_react.js?v=0b6b92cd:6756
getStreamedResponse @ ai_react.js?v=0b6b92cd:8255
getStreamedResponse @ ai_react.js?v=0b6b92cd:8372
processChatStream @ ai_react.js?v=0b6b92cd:7007
(anonymous) @ ai_react.js?v=0b6b92cd:8371
(anonymous) @ ai_react.js?v=0b6b92cd:8489
await in (anonymous)
sendMessage @ Chat.client.tsx:200
await in sendMessage
onClick @ BaseChat.tsx:249
onClick @ SendButton.client.tsx:23
callCallback2 @ chunk-TLFX46WQ.js?v=0b6b92cd:10552
invokeGuardedCallbackDev @ chunk-TLFX46WQ.js?v=0b6b92cd:10577
invokeGuardedCallback @ chunk-TLFX46WQ.js?v=0b6b92cd:10611
invokeGuardedCallbackAndCatchFirstError @ chunk-TLFX46WQ.js?v=0b6b92cd:10614
executeDispatch @ chunk-TLFX46WQ.js?v=0b6b92cd:13892
processDispatchQueueItemsInOrder @ chunk-TLFX46WQ.js?v=0b6b92cd:13912
processDispatchQueue @ chunk-TLFX46WQ.js?v=0b6b92cd:13921
dispatchEventsForPlugins @ chunk-TLFX46WQ.js?v=0b6b92cd:13929
(anonymous) @ chunk-TLFX46WQ.js?v=0b6b92cd:14052
batchedUpdates$1 @ chunk-TLFX46WQ.js?v=0b6b92cd:25791
batchedUpdates @ chunk-TLFX46WQ.js?v=0b6b92cd:10457
dispatchEventForPluginEventSystem @ chunk-TLFX46WQ.js?v=0b6b92cd:14051
dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ chunk-TLFX46WQ.js?v=0b6b92cd:12356
dispatchEvent @ chunk-TLFX46WQ.js?v=0b6b92cd:12350
dispatchDiscreteEvent @ chunk-TLFX46WQ.js?v=0b6b92cd:12327
Show 21 more frames
Show lessUnderstand this errorAI
logger.ts:84 ERROR Chat Request failed

Error
Chat.client.tsx:200 
        
       
       POST http://localhost:5174/api/chat 500 (Internal Server Error)
callChatApi @ ai_react.js?v=0b6b92cd:6756
getStreamedResponse @ ai_react.js?v=0b6b92cd:8255
getStreamedResponse @ ai_react.js?v=0b6b92cd:8372
processChatStream @ ai_react.js?v=0b6b92cd:7007
(anonymous) @ ai_react.js?v=0b6b92cd:8371
(anonymous) @ ai_react.js?v=0b6b92cd:8489
await in (anonymous)
sendMessage @ Chat.client.tsx:200
await in sendMessage
onKeyDown @ BaseChat.tsx:224
callCallback2 @ chunk-TLFX46WQ.js?v=0b6b92cd:10552
invokeGuardedCallbackDev @ chunk-TLFX46WQ.js?v=0b6b92cd:10577
invokeGuardedCallback @ chunk-TLFX46WQ.js?v=0b6b92cd:10611
invokeGuardedCallbackAndCatchFirstError @ chunk-TLFX46WQ.js?v=0b6b92cd:10614
executeDispatch @ chunk-TLFX46WQ.js?v=0b6b92cd:13892
processDispatchQueueItemsInOrder @ chunk-TLFX46WQ.js?v=0b6b92cd:13912
processDispatchQueue @ chunk-TLFX46WQ.js?v=0b6b92cd:13921
dispatchEventsForPlugins @ chunk-TLFX46WQ.js?v=0b6b92cd:13929
(anonymous) @ chunk-TLFX46WQ.js?v=0b6b92cd:14052
batchedUpdates$1 @ chunk-TLFX46WQ.js?v=0b6b92cd:25791
batchedUpdates @ chunk-TLFX46WQ.js?v=0b6b92cd:10457
dispatchEventForPluginEventSystem @ chunk-TLFX46WQ.js?v=0b6b92cd:14051
dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ chunk-TLFX46WQ.js?v=0b6b92cd:12356
dispatchEvent @ chunk-TLFX46WQ.js?v=0b6b92cd:12350
dispatchDiscreteEvent @ chunk-TLFX46WQ.js?v=0b6b92cd:12327
Show 21 more frames
Show lessUnderstand this errorAI
logger.ts:84 ERROR Chat Request failed

Error

I hope you can give assistance on this,

Thank You in Advance:)

threathunter369 · November 12, 2024, 8:33am

Hi Guys,

Upon running new instance of Ubuntu on My VMware, All newly download and install, but still can’t run the oTToDeve properly.

I’ve been getting this errors for about a week now:(

I have this errors again, anyone can give assistance on this?

Thank You

mahoney · November 15, 2024, 3:26am

Oh, I very much remember these minified react errors from the initial Bolt launch. Let me check my history, I think there is an issue posted from back then. Thanks for your patience.

mahoney · November 15, 2024, 3:31am

That’s right, the initial issues I saw that surfaced React minification errors were a direct result of any Chrome extension that attempts to modify the current page. In my case back then, I had to remove an extension related to using VR headsets in the browser

Can you please check your list of extensions for any that would have similar behavior? In order to fix my problem for sure, I went through each and switched them on/off while attempting to use the UI. Hopefully that’s it!

Edit: Your request failures may very likely be a separate issue, or not. Please report back with your results and if those still remain.

mahoney · November 15, 2024, 3:34am

Here is the React error page explaining what error 418 means.

Hydration failed because the server rendered HTML didn’t match the client. As a result this tree will be regenerated on the client. This can happen if a SSR-ed Client Component used:

A server/client branch if (typeof window !== 'undefined').
Variable input such as Date.now() or Math.random() which changes each time it’s called.
Date formatting in a user’s locale which doesn’t match the server.
External changing data without sending a snapshot of it along with the HTML.
Invalid HTML tag nesting.

It can also happen if the client has a browser extension installed which messes with the HTML before React loaded. ← This is the important bit.

Error 423 (“There was an error while hydrating but React was able to recover by instead client rendering the entire root.”) is likely a knock-on effect of the 418 error that results in the entire UI being re-rendered, most likely server-side. This should go away with 418 if the extension in question is disabled.

threathunter369 · November 15, 2024, 8:11am

Thank you very much,

I’ve been having this errors since last 2 weeks already can’t seem to figure it out on what is causing it. I already deploy it in a newly fired up Ubuntu VM newly installed everything but still not working. Maybe it has something to do with the VM network/adapter or firewall etc?

I even installed in my newly Formated Windows 11 , newly installed all requirements but still not working for me,

I hope i can make it work soon, Thank You I will try this out:)

threathunter369 · November 15, 2024, 8:55am

I still have errors, i have no extension in my browsers, i use the google chrome canary newly installed also. I also have my API keys in .env.local. Anthropic, OpenAI and Groq API’s .

See below screenshot of the errors,

And when i Type every letters on the prompt box the Ollama errors keep adding up:(

I don’t know how to solve them, haizt:(

ColeMedin · November 15, 2024, 5:42pm

@threathunter369 An internal server error means you’ll see better error logs in the terminal where you started oTToDev! I’d check there!

mahoney · November 15, 2024, 6:46pm

To address the screenshots (and thanks for taking them):

#2 (child key prop error): I’ve seen this, likely related to the provider dropdowns being populated, not a critical error. Making a note for this to get cleaned up.
#3 This is console logging leftover from a previous code update, not an error, and appears your model dropdown is populating correctly.
#4 The Chat.client.tsx and BaseChat.tsx line numbers don’t line up with what’s currently in main. For the time being until we have a release schedule, I would suggest keeping your local copy of the repo up to date with latest in main as core functionality issues are being addressed. Easiest way to do this is a git pull against your local copy, or a sync of your own fork if you have made one.

@ColeMedin is correct, and if you are receiving 500 errors from /api/chat those are likely also coming through from your Ollama instance. Please check the console for your local ollama provider, any errors there are going to be helpful.

ColeMedin · November 16, 2024, 3:38pm

Thanks for adding all of this @mahoney!