Hi Gabriele.

What automatic update?

What Apache is this that is sending this message?

Ist that your reverse proxy for EGroupware?

If so: What says your apache-error-log?

Stefan

Two customers also reporting that, do you have an error-message from the starting Rocket.Chat container:

error: "Can't find migration version 225"

What version are you using, what’s the output of:

grep image /etc/egroupware-rocketchat/docker-compose.override.yml

Ralf

Just tried the todays new version 3.14.5 which works ok for me and stayed on migration 222, like 3.14.4 before.

Is it possible you tried to downgrade from rocketchat/rocket.chat:latest to :3.14.x?

Downgrades are not supported by Rocket.Chat and lead to a crash / exit when starting the container!

If that’s the case, you can only go back to latest.

Please note our newer packages use no longer rocketchat/rocket.chat:latest but mirror their releases in our repository on quay.io2 and use now quay.io/egroupware/rocket.chat:stable, which we only assign after some testing.

If you want to move to quay.io/egroupware/rocket.chat:stable, you can use our script:
/etc/egroupware-rocketchat/move2stable.sh
Which compares the versions and only does the move, if it would not attempt a downgrade.

Ralf

That means rocketchat accidently pushed 3.14.5 as latest

Don’t know if they already fixed it or not.
You can try to pull again:

cd /etc/egroupware-rocketchat
docker-compose pull
docker-compose up -d
docker logs -f rocketchat # use Ctrl-C to stop tail after RC is started

If that still gives you the same error, Rocket.Chat has not yet fixed it and you can only fix the tag manually:

cd /etc/egroupware-rocketchat
sed 's/rocket.chat:latest/rocket.chat:3.15.0/' -i docker-compose.override.yml
docker-compose pull
docker-compose up -d
docker logs -f rocketchat # use Ctrl-C to stop tail after RC is started

And don’t forget to go back to stable latest tag, or better our quay.io/egroupware/rocket.chat:stable, to continue receiving updates.

Ralf

Rocket.Chat so far only supports MongoDB 4.0 and that’s what’s in our docker-compose.yml:

The other error from MongoDB init container is normal and unavoidable AFAIK, when using Watchtower. It simply means the previous running init container is no longer the latest mongo:4.0 version. This error can by safely ignored (in scripts I use: echo "y" | docker-compose up -d).

Please mark my first suggestion, simply pulling again, as solution.

Ralf

Use my script: /etc/egroupware-rocketchat/move2stable.sh

It checks if it’s save and only then migrates you to stable tag.

Ralf