#community-help

Addressing "ObjectNotFound" Error with HTTP Code 404

TLDR Jameshwart asks about a "ObjectNotFound" error with HTTP code 404, Kishore Nallan explains it could be due to a nonexistent collection or API end-point.

5mo

Join the chat

Apr 11, 2023 (5 months ago)

Photo of md5-283d3397742c32cc2b6be6bda508c03e

Jameshwart

05:44 AM

what is usually the issue if the error is "ObjectNotFound: Request failed with HTTP code 404 | Server said: Not found."?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

05:45 AM

Collection does not exist if you are trying to search.

05:45

Kishore Nallan

05:45 AM

Or the API end-point itself does not exist.

Jameshwart

05:47 AM

thanks a lot.

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Fixing "bad json" error in Typesense 0.24

Adam experiences "bad json" error when creating collections in Typesense 0.24. Jason identifies a typo in the docs causing the error and helps troubleshoot additional errors.

6mo

Troubleshooting Typesense Connection Issue and Data Retrieval

Felix encountered issues connecting to a server-created typesense and retrieving data collections. Kishore Nallan and Jason provided guidance, highlighting errors in the original code and suggesting changes to the URL and curl command.

20mo

Ingesting JSON Data and UnhandledPromiseRejectionWarning Error.

vikram had an issue concerning ingestion of data from local sources and facing error. Jason helped them realize the error was due to an existing collection, and they fixed the problem.

11mo