# Can't upgrade to 7 from 6 **URL:** \ **Category:** Upgrade Help\ **Created:** [December 14, 2024, 5:49am UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103 "2024-12-14T05:49:16Z")\ **Posts on this page:** 14\ **Page:** 2
**Author:** ![OneScripter](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/onescripter/32/5751_2.png) [@OneScripter](https://forums.rocket.chat/u/OneScripter)\ **Post date:** [January 7, 2025, 7:08pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/21 "2025-01-07T19:08:39Z")
Exact same issue here. Unable to upgrade from 6.13 to 7.x. Any news on a fix or proper upgrade procedure? ---
**Author:** ![Roy.Hess](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Roy.Hess](https://forums.rocket.chat/u/Roy.Hess)\ **Post date:** [January 9, 2025, 8:16am UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/22 "2025-01-09T08:16:30Z")
I do have the same issue in my own thread and no idea what to do now. Glad I pulled a dump from mongo before I started. Hope we can get help to solve this issue ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [January 9, 2025, 6:44pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/23 "2025-01-09T18:44:25Z")
> [@Roy.Hess](#): > > Glad I pulled a dump from mongo before I started. You don’t that on a regular basis anyway? 🤯🤦‍♂️ > [@Roy.Hess](#): > > Hope we can get help to solve this issue You mean you hope Rocket get to fix it for you? 🤷‍♂️ As per the bug. I have asked again but nothing yet. Remember Christmas probably cost 3+ weeks of time so everything is behind. ---
**Author:** ![Roy.Hess](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Roy.Hess](https://forums.rocket.chat/u/Roy.Hess)\ **Post date:** [January 9, 2025, 6:49pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/24 "2025-01-09T18:49:31Z")
you are not helping… Also: I do daily backups automatically, since there had been activity on the chat, I decided to pull a dump just to be safe. You didn’t realize that users are active on chats, do you? ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [January 9, 2025, 7:20pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/25 "2025-01-09T19:20:21Z")
> [@Roy.Hess](#): > > you are not helping… I’m not a dev though I know most of them very well. Let us know your server details including licence type. If you have paid support, use it. If not you are in the lap of the gods. The nature of open source. > [@](#): > > Also: I do daily backups automatically, since there had been activity on the chat, I decided to pull a dump just to be safe Excellent. You didn’t make that clear. > [@](#): > > You didn’t realize that users are active on chats, do you? As (non employed/non paid) Community Liaison and moderator here and open.rocket.chat I’m perfectly aware thanks. You also might like to know that noapparent activity I’m the one that has been pushing in the background for a solution as I speak pretty well all day every day with several Rocket employees. However, I also have a day job and don’t control the dev, eng & product teams. And Rocket also have paying customers that will come first. ---
**Author:** ![Roy.Hess](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Roy.Hess](https://forums.rocket.chat/u/Roy.Hess)\ **Post date:** [January 9, 2025, 8:05pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/26 "2025-01-09T20:05:47Z")
sorry for being a bit rude but your “facepalm” emotes triggered me, as well as rocket chat failing to update **to 6.4.0/stable** from **6.13.0/stable** or updating **to 7.0.0/stable** from **6.13.0/stable** using the command: **sudo snap switch --channel=latest/stable rocketchat-server** to switch to the 6.4.0 stable channel and then issuing **sudo snap refresh rocketchat-server** This doesn’t result in errors, but even when manually starting the server, nothing starts and no listener listens on 3000 if I revert it works fine again. I have tried both versions, rocketchat-server is not starting up at all when in 6.4.0 or 7.0.0 and journalctl does not give any useful information when trying to start either version. Only mentions **caddy** which I don’t use (i use a perfectly fine working nginx) and have disabled in env (yet it still appears in log file) If I revert back to **6.13.0** it starts up fine again, but mentions that it is supported until may, 1st 2025 and it frustrates me quite a lot not knowing what the issue really is. community license, can’t afford a higher license due to very high costs that aren’t worth for what we would get in return for a private small community **Apps Engine v:** 1.46.0 **Node:** v14.21.2 **database migration:** 304 (January 9, 2025 20:40) **MongoDB:** 5.0.15 / wiredTiger (oplog Enabled) ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [January 11, 2025, 2:26pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/27 "2025-01-11T14:26:33Z")
Check this issue comment: > > > \### Description: > > Cant update via snap from 6.13.0 to 7.0 \*\*edited\*\* > > \### St…eps to reproduce: > > 1. Switch to relase chanel 7.x > 2. Snap refresh rocketchat-server > 3. The server return: Start snap "rocketchat-server" (1633) services (systemctl command \[start snap.rocketchat-server.rocketchat-mongo.service\] failed with exit status 1: stderr: > > \### Expected behavior: > > Update to 7.0 \*\*edited\*\* > > \### Actual behavior: > > !\[image\](https://github.com/user-attachments/assets/163601b8-fc5d-45f8-bef7-34135757dfca) > > \### Server Setup Information: > > \- Version of Rocket.Chat Server: 6.13.0 > \- License Type: free > \- Number of Users: 40 > \- Operating System: Ubuntu 20.04 > \- Deployment Method: snap > \- Number of Running Instances: > \- DB Replicaset Oplog: > \- NodeJS Version: > \- MongoDB Version: > > \### Client Setup Information > > \- Desktop App or Browser Version: > \- Operating System: > > \### Additional context > > > > \### Relevant logs: > Here is the logs from server after error: > > systemctl status snap.rocketchat-server.rocketchat-mongo.service (logs) > https://pastejustit.com/asbx1cexen > > journalctl -xe (logs) > https://pastejustit.com/yuyrbyesza I have asked the team as to why this happens - it should be taken care of automagically. ---
**Author:** ![Roy.Hess](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Roy.Hess](https://forums.rocket.chat/u/Roy.Hess)\ **Post date:** [January 11, 2025, 3:16pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/28 "2025-01-11T15:16:00Z")
no bueno here, after issuing: sudo snap run rocketchat-server.mongo show dbs use parties (yes my instance uses “parties”) db.adminCommand({ setFeatureCompatibilityVersion: “5.0” }); exit sudo snap switch --channel=7.x/stable rocketchat-server sudo snap refresh rocketchat-server I am getting the errors: ```auto /snap/rocketchat-server/1634/helpers/mongo.sh: line 50: ((: {"t":{"$date":"2025-01-11T15:15:08.358Z"},"s":"I", "c":"NETWORK", "id":5693100, "ctx":"js","msg":"Asio socket.set_optioailed with std::system_error","attr":{"note":"connect (sync) TCP fast open","option":{"level":6,"name":30,"data":"01 00 00 00"},"error":{"what":"set_option: Protocol not available",ssage":"Protocol not available","category":"asio.system","value":92}}} 1 : syntax error: operand expected (error token is "{"t":{"$date":"2025-01-11T15:15:08.358Z"},"s":"I", "c":"NETWORK", "id":5693100, "ctx":"js","msg":"Asio socket.set_option failedth std::system_error","attr":{"note":"connect (sync) TCP fast open","option":{"level":6,"name":30,"data":"01 00 00 00"},"error":{"what":"set_option: Protocol not available","messageProtocol not available","category":"asio.system","value":92}}} 1 ") [ERROR] mongod server start wait timed out [ERROR] pre refresh migration script /snap/rocketchat-server/1634/migrations/pre_refresh/feature_compatibity/00-adopt_version.sh -----) ``` Dont know what this means or what I can do. ---
**Author:** ![Roy.Hess](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Roy.Hess](https://forums.rocket.chat/u/Roy.Hess)\ **Post date:** [January 11, 2025, 3:51pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/29 "2025-01-11T15:51:03Z")
I got it to work, somehow, here is what I have done prior to setting the feature compatibility to 5.0: **just for safety, a mongodump:** snap run rocketchat-server.backupdb **stopping the snap:** snap stop rocketchat-server **refreshing diretly to a new channel:** snap refresh rocketchat-server --channel=7.x/stable console output: `rocketchat-server (7.x/stable) 7.0.0 von Rocket.Chat (rocketchat✓) aufgefrischt` **restarting rocketchat-server** snap start rocketchat-server Seems to be running, for some strange reason, even though the service is disabled, masked in systemd and disabled in snap, caddy is still running, even though I have stopped it prior: snap info rocketchat-server `rocketchat-server.rocketchat-caddy: simple, disabled, active` ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [January 11, 2025, 6:05pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/30 "2025-01-11T18:05:10Z")
> [@Roy.Hess](#): > > use parties (yes my instance uses “parties”) FWIW all snaps do - historical reasons. Docker does not. > [@](#): > > caddy is still running Was it before? Has this started after the upgrade? Not sure which caddy version you are using but this is the doc. Please advise if this right or wrong. [https://docs.rocket.chat/v1/docs/deploy-with-snaps](https://docs.rocket.chat/v1/docs/deploy-with-snaps) ---
**Author:** ![pdarko](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/pdarko/32/5903_2.png) [@pdarko](https://forums.rocket.chat/u/pdarko)\ **Post date:** [April 14, 2025, 11:21am UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/31 "2025-04-14T11:21:29Z")
I got same error, and got it down to faulty mongo\_eval function in mongo.sh: `mongo --quiet --eval "${1?}"` mongo returns extra line which mongo\_eval returns (instead of just 1) when called for ping: ```auto rocketchat-server.mongo --quiet --eval 'db.adminCommand({ ping: 1 }).ok' {"t":{"$date":"2025-04-14T11:15:41.330Z"},"s":"I", "c":"NETWORK", "id":5693100, "ctx":"js","msg":"Asio socket.set_option failed with std::system_error","attr":{"note":"connect (sync) TCP fast open","option":{"level":6,"name":30,"data":"01 00 00 00"},"error":{"what":"set_option: Protocol not available","message":"Protocol not available","category":"asio.system","value":92}}} 1 ``` This could easy be fixed by changing mongo\_eval… which i can’t in a snap, so refresh fails. I tried setting net.ipv4.tcp\_fastopen to 3 or even 0, but didn’t help. ---
**Author:** ![pdarko](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/pdarko/32/5903_2.png) [@pdarko](https://forums.rocket.chat/u/pdarko)\ **Post date:** [April 15, 2025, 10:48am UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/32 "2025-04-15T10:48:59Z")
And for anyone with same problem, migrating to new host/distro (ol7-\>9) removed mongo extra line, and snap refresh worked. ---
**Author:** ![makasyan](https://avatars.discourse-cdn.com/v4/letter/m/91b2a8/32.png) [@makasyan](https://forums.rocket.chat/u/makasyan)\ **Post date:** [April 17, 2025, 4:37am UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/33 "2025-04-17T04:37:33Z")
at your own risk **sudo snap set rocketchat-server ignore-errors=true** after that sudo snap refresh rocketchat-server ---
**Author:** ![malou](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/malou/32/5916_2.png) [@malou](https://forums.rocket.chat/u/malou)\ **Post date:** [April 26, 2025, 5:31pm UTC](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103/34 "2025-04-26T17:31:31Z")
> [@pdarko](#): > > And for anyone with same problem, migrating to new host/distro (ol7-\>9) removed mongo extra line, and snap refresh worked. Thanks! This sent me on the right track. Upgrading the OS to a newer version solve the issue. [Previous page](https://forums.rocket.chat/t/cant-upgrade-to-7-from-6/21103.md?page=1)