# DB and env related issues while upgrading existing instance to 3.0.0

**URL:** <https://community.datagerry.com/t/db-and-env-related-issues-while-upgrading-existing-instance-to-3-0-0/830>\
**Category:** Community Support\
**Created:** [November 26, 2025, 4:22pm UTC](https://community.datagerry.com/t/db-and-env-related-issues-while-upgrading-existing-instance-to-3-0-0/830 "2025-11-26T16:22:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![skriegler-aptean](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@skriegler-aptean](https://community.datagerry.com/u/skriegler-aptean)\
**Post date:** [November 26, 2025, 4:22pm UTC](https://community.datagerry.com/t/db-and-env-related-issues-while-upgrading-existing-instance-to-3-0-0/830/1 "2025-11-26T16:22:14Z")

</div>

Hi everyone. I want to upgrade our existing instance to 3.0.0 and am facing several issues. None of the release notes ( [DataGerry | Release 3.0.0](https://datagerry.com/datagerry-release-3-0-0/) , [Changelogs — DataGerry latest documentation](https://docs.datagerry.com/en/latest/sources/changelog.html#version-3-0-0) ) mentions a breaking change in the config file and how environment variables are handled between 1.7.2 and 3.0.0

Right now I am passing following environment variables into the Docker Container:

- DATAGERRY\_Database\_host

- DATAGERRY\_Database\_password
- DATAGERRY\_Database\_username
- DATAGERRY\_MessageQueueing\_host
- DATAGERRY\_MessageQueueing\_password
- DATAGERRY\_MessageQueueing\_username

I already found that RabbitMQ is not needed anymore.

By experimenting I found that the database related environment variables are not processed anymore, or at least don’t overwrite the defaults from /etc/datagerry/cmdb.conf. Am I missing something?

A second issue seems to be that I am not able to connect to a mongodb instance that requires authentication. Am I missing something?

Thanks in advance for your answers.

---

<div class="post-metadata">

**Author:** ![skriegler-aptean](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@skriegler-aptean](https://community.datagerry.com/u/skriegler-aptean)\
**Post date:** [December 5, 2025, 8:45pm UTC](https://community.datagerry.com/t/db-and-env-related-issues-while-upgrading-existing-instance-to-3-0-0/830/2 "2025-12-05T20:45:48Z")

</div>

Figured it out by inspecting the codebase. I had to drop all above environment variables and just use `CONNECTION_STRING` environment variable, containing the mongodb connection string including authentication. 🥳

---

<div class="post-metadata">

**Author:** ![adnan.smajic](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/adnan.smajic/32/754_2.png) [@adnan.smajic](https://community.datagerry.com/u/adnan.smajic)\
**Post date:** [February 2, 2026, 4:26pm UTC](https://community.datagerry.com/t/db-and-env-related-issues-while-upgrading-existing-instance-to-3-0-0/830/3 "2026-02-02T16:26:56Z")

</div>

Hi @skriegler-aptean ,

the complete env variables section for DataGerry will be improved and documented as part of version 3.2.

Sincerly,

Your DataGerry-Team