AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Rocketchat desktop app4/17/2023 You can choose to run analytics on your team messaging app daily or even hourly. Multifactor authentication is also available with some of the paid plans, which is helpful for security purposes. ![]() You can pay more to do that twice daily or every hour, but the question is whether that’s really valuable. One example of this is that the Bronze, Silver, and Gold versions all allow you to do an automated backup of the entire platform. If you haven't check it out.There are so many features in Rocket.Chat as part of the various paid plans that it’s hard to know where to begin, and there are questions about whether anyone would really take advantage of them. Rocket.Chat is a really good open-source communication and collaboration tool. Anyway, if you are still running an older server version then it’s about time you plan your upgrade soon! Instead, they went the other route and forced everyone to upgrade immediately. Rocket.Chat Team should have kept the backward compatibility with the older server version and gave a deadline to act. This “hack” allows your team some breathing space while you start planning on upgrading the Rocket.Chat server version. WARNING! Do not use this “hack” as a permanent fix. Your users should now be able to connect to the server and use the latest Rocket.Chat Desktop normally. Not surprisingly, it will connect even though the server is still running an older version. With this simple change, if you now try connecting to the server using the latest Rocket.Chat Desktop version. Fixed Response rule added to AWS ALBĪnd voila! we’ve upgraded the server in the eyes of Rocket.Chat Desktop. If you have deployed Rocket.Chat server behind AWS load-balancer then we can add a custom rule and craft a custom JSON response using Fixed Response feature of AWS ALB.įig. 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. I began drilling into the Rocket.Chat Desktop source code to figure out how Server validation is actually performed under the hood. 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. 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.
0 Comments
Read More
Leave a Reply. |