# Server Reports as being Mongo API Verson 2.4

**URL:** <https://forums.foundationdb.org/t/server-reports-as-being-mongo-api-verson-2-4/1079>\
**Category:** Document Layer\
**Created:** [January 29, 2019, 5:05pm UTC](https://forums.foundationdb.org/t/server-reports-as-being-mongo-api-verson-2-4/1079 "2019-01-29T17:05:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![developer\_resource](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@developer\_resource](https://forums.foundationdb.org/u/developer_resource)\
**Post date:** [January 29, 2019, 5:05pm UTC](https://forums.foundationdb.org/t/server-reports-as-being-mongo-api-verson-2-4/1079/1 "2019-01-29T17:05:01Z")

</div>

Hi,

When using the MongoDB Client against the Document Layer we noticed that the server returns a response that says it is Mongo API v2.4, why is that?

```
MongoDB shell version v3.6.5
connecting to: mongodb://ingress.domainname.cloud:4100
MongoDB server version: 2.4.10
WARNING: shell and server versions do not match
Server has startup warnings:

WARNING: This is not really mongodb.
```

---

<div class="post-metadata">

**Author:** ![mbhaskar](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/mbhaskar/32/277_2.png) [@mbhaskar](https://forums.foundationdb.org/u/mbhaskar)\
**Post date:** [January 29, 2019, 5:26pm UTC](https://forums.foundationdb.org/t/server-reports-as-being-mongo-api-verson-2-4/1079/2 "2019-01-29T17:26:54Z")

</div>

Good catch! That’s a bug in `buildInfo` command response. I have created an issue for this

> <https://github.com/FoundationDB/fdb-document-layer/issues/54>

---

<div class="post-metadata">

**Author:** ![mbhaskar](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/mbhaskar/32/277_2.png) [@mbhaskar](https://forums.foundationdb.org/u/mbhaskar)\
**Post date:** [February 18, 2019, 10:33pm UTC](https://forums.foundationdb.org/t/server-reports-as-being-mongo-api-verson-2-4/1079/3 "2019-02-18T22:33:11Z")

</div>

This is fixed and merged into master now. It should be released part of 1.6.3.