rightstand.blogg.se - Give rocketchat server a url

#Give rocketchat server a url update#
#Give rocketchat server a url upgrade#
#Give rocketchat server a url software#
#Give rocketchat server a url code#

Well, what if we modify the JSON response on the fly and return a version ≥ 2.0.0 without upgrading the server. The version information is then parsed from JSON response and is compared against the hard-coded REQUIRED_SERVER_VERSION_RANGE. If you curl this endpoint, it’ll return the server version information as JSON response: 18, the server version information is fetched by requesting api/info endpoint.

#Give rocketchat server a url code#

I began drilling into the Rocket.Chat Desktop source code to figure out how Server validation is actually performed under the hood.

#Give rocketchat server a url upgrade#

But in reality, this is not feasible when you have 100s of users!Īlright, we know the upgrade is mandatory but not possible overnight. One of the possible workarounds is to request end-users to re-install the older version of Rocket.Chat Desktop < 3.0.0, which doesn’t perform the Server Validation.

#Give rocketchat server a url software#

However, an overnight server upgrade is not possible for any production software unless it’s Heartbleed of course.

Many users and companies who are running Rocket.Chat server version < 2.0.0 in production is suddenly left with one option, UPGRADE! “You are connecting to the server that is running an older version and is no longer supported. A more appropriate message would have been: Secondly, this message has nothing to do with the server version. If you try connecting to Rocket.Chat server running an older version, you’ll be prompted with the following message.įirstly, the message is vague and unclear, and at first, the user will try to double-check if they have entered the correct URL. With this breaking change, Rocket.Chat Desktop will no longer work on Rocket.Chat Server running on version < 2.0.0. In this release Rocket.Chat team introduced Server validation and hard-coded the minimum required Rocket.Chat server version of 2.0.0. Rocket.Chat Desktop recently released version 3.0.2. Now it works!!! after spending several hours on this. Now start the server again: $ service -server startĬheck the status: $ service -server status $ snapctl get snap-refreshing #which returned "true"

#Give rocketchat server a url update#

So I guess there is an error in this new version, have to roll it back to previous version and forbid it to update the latest version: $ snap revert -revision=1427 rocketchat-server But the old version 1427 has it: /snap/rocketchat-server/1427/ When I cd to /snap/rocketchat-server/1436/ folder, there is no "star.json" file. Return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode) Įrror: ENOENT: no such file or directory, open '/snap/rocketchat-server/1436/star.json' By checking its log: journalctl -u -server To start the rocket.chat server, it still doesn't work. The MongoDB is running, but when I use: service -server start

once it is done, try start rocketchat-mongo: service -mongo start, then check its status again: service -mongo status, it should be running now.

mongod -repair -dbpath /var/snap/rocketchat-server/common/

cd to /snap/rocketchat-server/current/bin.

now is the key part, run commnad: db.adminCommand( ).

in the same 3.6 bin folder, use mongo connect to the server.

mongod -dbpath /var/snap/rocketchat-server/common/

Download version 3.6 in mongodb's website.

Now the database files cannot be run under mongo3.4 anymore (which rver needs). It turns out snap did an update to our rocket.chat server, and updated it to the new version, which now runnign mongodb version 3.6 and changed some database files. WiredTiger error (-31802), txn-recover: unsupported WiredTiger file version: this build only supports major/minor versions up to 1/0, and the file is version 2/0: WT_ERROR: non-specific WiredTiger error There are some errors about the versioning: When I check the mongo start log with command: journalctl -u -mongo So apparently there is something wrong with MongoDB. When I check the server, use the command to check status of rocketchat server and its mongo: $ service -server status Today our self-hosted rocket.chat server suddenly stopped running, and it turns out I am not the only one experiencing this problem