Rocket.Chat Version / DB Upgrade

Rocket.Chat Upgrade Issue (MongoDB 7 → 8, 8.1.1 → 8.2.1)

Current setup

  • Rocket.Chat: 8.1.1

  • MongoDB: 7.0

  • Running stable with full data (users, channels, messages)

Goal

Upgrade to:

  • Rocket.Chat 8.2.1

  • MongoDB 8

Test setup

  • MongoDB 8

  • Rocket.Chat 8.1.1 works fine on MongoDB 8

Problem

After upgrading Rocket.Chat to 8.2.1 (changing only the image in docker-compose):

  • Rocket.Chat starts

  • Setup wizard appears

  • Asked to create a new admin account

  • Existing data is not recognized

What I tried

  1. Direct upgrade (8.1.1 → 8.2.1)
    → Setup wizard appears

  2. Backup & restore:

    mongodump --gzip --archive=dump.gz
    mongorestore --gzip --archive=dump.gz --drop
    
    

    → Data is restored but still not recognized

  3. Combinations:

    • MongoDB 8 + Rocket.Chat 8.1.1 → works

    • MongoDB 8 + Rocket.Chat 8.2.1 → setup wizard

Question

Is there a required migration step when upgrading from Rocket.Chat 8.1.1 (MongoDB 7) to 8.2.1 (MongoDB 8)?

How can I upgrade without losing or reinitializing the existing data?

You only need to post once.

Have you read all the docs?

Have you read all the docker mongo docs?

Did you read the release notes BEFORE upgrading and do what they told you? If you didn’t breakages may occur.

….and workspaces must upgrade to MongoDB 8.2 before moving to Rocket.Chat v8.0.0, with a full backup strongly recommended.

Think that is quite clear?

Have you got good backups? You may need them.

Full text here.

Hey sorry for posting twice!

ive read all the release notes and patch notes.

I tried launching rocket.chat on a local machine to test the migration first, i got MongoDB to version 8 on rocketchat. 8.1.1, but when i try to install 8.2.x, i get the /setup-wizard all the time.

Thank you for ur answer!

More like a docker issue than a Rocket one.

Sounds like your db didn’t upgrade correctly. Logs are your friend…. What do they say? Both Rocket & Mongo?

You need to check the mongo docs on upgrading the db. If you didn’t set it you might want to look for :

setFeatureCompatibilityVersion