Unable to log in to Rocket.Chat Cloud via the Connectivity Services setting

Description:

Hey guys!

I can't log in to Rocket.Chat cloud via my instance.

Sync says it’s working when I press the button, which may be true, but when I click the Login to Rocket.Chat Cloud button, it takes me to the Authorization screen, where I receive the “error-invalid-state” error when I press the Authorize button

This means I can't use apps and other things that rely on this.

There was already a forum post made regarding this issue you can see here:

https://forums.rocket.chat/t/error-in-push-notifications-cloud-registration-error/14940

Along with the support thread for unRAID here:

https://forums.unraid.net/topic/61337-support-rocketchat/page/6/

I can mostly confirm that this is NOT an unRAID specific issue as a user on a different platform and using the latest version of Rocket.Chat (unavailable to us unRAIDers just yet) is also having the same issue in that thread

Steps to reproduce:

1. Go to Administration
2. Go to Connectivity Services
3. Click on "Login to Rocket.Chat Cloud"
4. Sign in and click on "Authorize"

Expected behavior:

Successful login to Rocket.Chat Cloud and begin using services like apps

Actual behavior:

Be returned to the settings screen and receive error "error-invalid-state"

Server Setup Information:

Version of Rocket.Chat Server: 5.0.3
Operating System: Unraid/Linux
Deployment Method: docker
NodeJS Version: 14.19.3 - x64
MongoDB Version: 6.0.1

Relevant logs:

Log from server when receiving the error:

{"level":50,"time":"2022-09-26T06:17:22.311Z","pid":1,"hostname":"0b8fd1acb48a","name":"System","msg":"Exception while invoking method cloud:finishOAuthAuthorization 'Invalid state provided [error-invalid-state]'"}

Start by reproducing the Administration > Connectivity Services login flow and inspect the server log for cloud:finishOAuthAuthorization and its “Invalid state provided” error. Trace the authorization state from the Login to Rocket.Chat Cloud action through the Authorize callback; done means the flow completes successfully without error-invalid-state.