# Weaviate "update vector: unmarshal error response body: Not Found" on Object Creation with text2vec-huggingface

**URL:** <https://forum.weaviate.io/t/weaviate-update-vector-unmarshal-error-response-body-not-found-on-object-creation-with-text2vec-huggingface/21059>\
**Category:** Support\
**Tags:** bug, technical\
**Created:** [May 15, 2025, 6:37pm UTC](https://forum.weaviate.io/t/weaviate-update-vector-unmarshal-error-response-body-not-found-on-object-creation-with-text2vec-huggingface/21059 "2025-05-15T18:37:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![manuharari](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/manuharari/32/4097_2.png) [@manuharari](https://forum.weaviate.io/u/manuharari)\
**Post date:** [May 15, 2025, 6:37pm UTC](https://forum.weaviate.io/t/weaviate-update-vector-unmarshal-error-response-body-not-found-on-object-creation-with-text2vec-huggingface/21059/1 "2025-05-15T18:37:54Z")

</div>

### Description

Hello everyone,

I’m encountering a persistent error when trying to create objects in my Weaviate instance, and I’m hoping someone in the community might have some insights.

**The Error:**

Every time I attempt a `POST` request to `/v1/objects` for my `MunicipioPdf` class, the Weaviate logs show the following error:

`{"action":"requests_total","api":"rest","class_name":"MunicipioPDF","error":"update vector: unmarshal error response body: Not Found","level":"error","msg":"unexpected error","query_type":"objects","time":"..."}`

This error occurs immediately after the `POST` request is received by Weaviate.

[⚠ Suspicious Content] Our Architecture and Language:

Backend Language: Java (using Spring Boot and the spring-webflux WebClient for interacting with Weaviate).  
Weaviate Setup: Running Weaviate in a Docker container (version 1.26.0, as per the logs). The text2vec-huggingface module also appears to be running within the same Weaviate container (based on the logs).  
Vectorizer Model: We are using the sentence-transformers/all-mpnet-base-v2 model specified in our Weaviate schema for the MunicipioPdf class.  
Our Weaviate Schema for the MunicipioPdf Class:

JSON

{  
“classes”: [  
{  
“class”: “MunicipioPdf”,  
“description”: “PDF chunks from Municipio documents”,  
“vectorizer”: “text2vec-huggingface”,  
“vectorizeClassName”: false,  
“moduleConfig”: {  
“text2vec-huggingface”: {  
“model”: “sentence-transformers/all-mpnet-base-v2”  
}  
},  
“properties”: [  
{  
“name”: “filename”,  
“dataType”: [“text”],  
“description”: “Name of the PDF file”,  
“tokenization”: “word”,  
“indexInverted”: true,  
“indexFilterable”: true,  
“indexSearchable”: true,  
“vectorizePropertyName”: false,  
“skipVectorization”: true  
},  
{  
“name”: “content”,  
“dataType”: [“text”],  
“description”: “Text content chunk extracted from the PDF”,  
“tokenization”: “word”,  
“indexInverted”: true,  
“indexFilterable”: false,  
“indexSearchable”: true,  
“vectorizePropertyName”: false,  
“skipVectorization”: false  
},  
{  
“name”: “chunkIndex”,  
“dataType”: [“int”],  
“description”: “Index of the chunk within the PDF”,  
“indexInverted”: true,  
“indexFilterable”: true,  
“indexSearchable”: false,  
“vectorizePropertyName”: false,  
“skipVectorization”: true  
}  
]  
}  
]  
}

DOCKER

sudo docker run -d   
-p 8181:8080   
-e AUTHENTICATION\_ANONYMOUS\_ACCESS\_ENABLED=true   
-e PERSISTENCE\_DATA\_PATH=“/var/lib/weaviate”   
-e ENABLE\_MODULES=text2vec-huggingface   
-e DEFAULT\_VECTORIZER\_MODULE=text2vec-huggingface   
-e HUGGINGFACE\_APIKEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX   
-e HF\_HOME=“/var/lib/weaviate/hf\_cache”   
-e TEXT2VEC\_HUGGINGFACE\_MODEL=“sentence-transformers/all-mpnet-base-v2”   
-e TEXT2VEC\_HUGGINGFACE\_ENDPOINT=“[https://api-inference.huggingface.co/pipeline/feature-extraction/sentence-transformers/all-mpnet-base-v2](https://api-inference.huggingface.co/pipeline/feature-extraction/sentence-transformers/all-mpnet-base-v2)”   
-e QUERY\_DEFAULTS\_LIMIT=25   
-e LOG\_LEVEL=debug   
–name weaviate-huggingface-4   
semitechnologies/weaviate:1.26.0

Things We’ve Tried:

We’ve confirmed that our Java application can successfully connect to Weaviate for reading objects.  
Even a simple curl POST request to create a basic MunicipioPdf object with just filename and content fails with the same error in the Weaviate logs.  
We’ve reviewed the Weaviate container logs (weaviate-huggingface-4), and during startup, the text2vec-huggingface module appears to initialize correctly without any immediate errors related to permissions, API keys, or network issues.

Our Question:

Has anyone encountered this “update vector: unmarshal error response body: Not Found” error specifically during object creation with the text2vec-huggingface module? What could be causing Weaviate to fail during the vector update with a “Not Found” error, even for basic object creation? Any suggestions on where to look next for debugging this issue would be greatly appreciated!

Thank you in advance for your help!

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [May 15, 2025, 6:53pm UTC](https://forum.weaviate.io/t/weaviate-update-vector-unmarshal-error-response-body-not-found-on-object-creation-with-text2vec-huggingface/21059/2 "2025-05-15T18:53:13Z")

</div>

Hi @manuharari !!

I believe this issue is related to this PR:

> <https://github.com/weaviate/weaviate/pull/8095>
>
> \### What's being changed:
> 
> HuggingFace's feature extraction API has changed, t…his PR adjust HF module to support newest HF's API.
> 
> \### Review checklist
> 
> \- \[\] Documentation has been updated, if necessary. Link to changed documentation:
> \- \[\] Chaos pipeline run or not necessary. Link to pipeline:
> \- \[\] All new code is covered by tests where it is reasonable.
> \- \[\] Performance tests have been run or not necessary.

Note that this PR was backported only to 1.28.15:

> **[Release v1.28.15 - HuggingFace and Mistral vectorizer modules Fixes, Mmap...](https://github.com/weaviate/weaviate/releases/tag/v1.28.15)**
>
> Breaking Changes
> none
> New Features
> non
> Fixes
> 
> Improve names in bloom filter by @dirkkul in #8080
> chore: update text2vec-huggingface module to support newest API by @antas-marcin in #8095
> chore: upd...

I noticed you are using a really old version, 1.26.0

So I suggest you to upgrade path:

1.26.0 → 1.26.latest → restart → 1.27.latest → restart → 1.28.latest

in between each restart, wait all the data get loaded and the cluster stabilized.

Or, of your data is not too big, you can copy your data over to a new cluster running the latest version or the target version.

Let me know if this helps!

Thanks!

---

<div class="post-metadata">

**Author:** ![manuharari](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/manuharari/32/4097_2.png) [@manuharari](https://forum.weaviate.io/u/manuharari)\
**Post date:** [May 15, 2025, 9:03pm UTC](https://forum.weaviate.io/t/weaviate-update-vector-unmarshal-error-response-body-not-found-on-object-creation-with-text2vec-huggingface/21059/3 "2025-05-15T21:03:58Z")

</div>

> [@DudaNogueira](#):
>
> I believe this issue is related to this PR:

I did this, now what? i dont get what changed in the PR, can you help me?

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [May 15, 2025, 9:18pm UTC](https://forum.weaviate.io/t/weaviate-update-vector-unmarshal-error-response-body-not-found-on-object-creation-with-text2vec-huggingface/21059/4 "2025-05-15T21:18:03Z")

</div>

Hi! What version specifically have you upgraded to?

Also, we suggest running using a docker compose, such as:

> **[Docker | Weaviate](https://weaviate.io/developers/weaviate/installation/docker-compose#sample-docker-compose-file)**
>
> Weaviate supports deployment with Docker.

---

<div class="post-metadata">

**Author:** ![manuharari](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/manuharari/32/4097_2.png) [@manuharari](https://forum.weaviate.io/u/manuharari)\
**Post date:** [May 15, 2025, 11:52pm UTC](https://forum.weaviate.io/t/weaviate-update-vector-unmarshal-error-response-body-not-found-on-object-creation-with-text2vec-huggingface/21059/5 "2025-05-15T23:52:25Z")

</div>

It is now (apparently) loading the documents! it is sending an error though, a different one, but huge progress. You are sensational!!

Also want to know why does the update version needs to follow a path?

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [May 15, 2025, 11:59pm UTC](https://forum.weaviate.io/t/weaviate-update-vector-unmarshal-error-response-body-not-found-on-object-creation-with-text2vec-huggingface/21059/6 "2025-05-15T23:59:33Z")

</div>

That’s great news!!

That’s because there may - or may not - have migrations between versions.

Upgrading to the latest on each X.X will ensure you have everything needed to perform the next step.

A rule of thumb is to always be on X.x.latest and at least 3 versions behind the latest release.

For example, our current latest is 1.30, this last patch was back ported to 1.28.latest.

Now if you are on 1.28 and we release 1.31, all future patches will be back ported to 1.30 and 1.29

Let me know if this helps!

Happy coding!