Rocket.chat.electron: 3.0.4 Invalid server url

Created on 19 Oct 2020  路  13Comments  路  Source: RocketChat/Rocket.Chat.Electron

My Setup

  • Operating System: macOS 10.15.7
  • App Version: 3.0.4
  • Installation type: dmg (downloaded from github, fresh install)

  • [x] I have tested with the latest version
  • [x] I can simulate the issue easily

Description

Impossible to connect to my server : https://chat.my-company.com/ (dummy url, real one works when accessed from a browser).

Current Behavior

Got the error :

No valid server found at this url
(translated from French)

Expected Behavior


To connect to the server with no error, as before v3.

Most helpful comment

Workaround:

  1. Add servername as suggested by the app: "open.rocket.chat", do not enter any credentials there.
  2. Close the app
  3. Open ~/.config/Rocket.Chat/config.json
  4. Replace all occurrences of "open.rocket.chat" with your server's name
  5. Open the app again
  6. Click on the rocket chat icon in the navigation, 茅t voil脿 you should be placed to the login mask of your server
  7. Login to the rocket chat server as usual
    Whatever the client does when checking the initial entered URL, it doesn't when it's already configured.

Hope that helps someone else :)

All 13 comments

I have the same issue. I noticed a commit that I think suggests a change in minimum server version. Maybe that is the issue here, or would I expect another error then?

EDIT: Hmm. Seems like there is no change between 3.0.3 and 3.0.4 in minimum version number. Only that our server seems to have a lower version than required by either (0.74.3).

@ygrange Yes, it's the server version.

So it seems that the check of the server version has been fixed in 3.0.4; it would be useful to have a line in the changelog to make it explicit. (I have no clue wether changing the changelog text for a current release os considered good practice...)

Same problem here. Probably not the same bug as #1743 since that one should have been fixed in 3.3 (but I was unable to test due to bug reported in #1821 which was fixed in 3.4).

My server version is 1.0.2 with apps engine version 1.4.2.

Continue to have same problem w/ 3.0.4. Unsure what version server is running since I don't run it (but presume there is a way to check via web client?) Other users @ same group have had to revert back to 2.x.

Edit - I believe my server version is 1.2.4, which I see if I go to 'admin鈫抜nfo' (which is all I can 'see' there)

General comment for whoever ends up here: If you want to find out and do not have access to the admin panel, you can check chat./api/info

Workaround:

  1. Add servername as suggested by the app: "open.rocket.chat", do not enter any credentials there.
  2. Close the app
  3. Open ~/.config/Rocket.Chat/config.json
  4. Replace all occurrences of "open.rocket.chat" with your server's name
  5. Open the app again
  6. Click on the rocket chat icon in the navigation, 茅t voil脿 you should be placed to the login mask of your server
  7. Login to the rocket chat server as usual
    Whatever the client does when checking the initial entered URL, it doesn't when it's already configured.

Hope that helps someone else :)

Workaround:
...

  1. Open ~/.config/Rocket.Chat/config.json
    ...

~/Library/Application\ Support/Rocket.Chat/config.json for the macOS users

@kyoshiro This works for me, too, thanks for the workaround!

4. Replace all occurrences of "open.rocket.chat" with your server's name

i didn't find any recurrence of "open.rocket.chat" in my config.json any help plzzzzz

  1. Replace all occurrences of "open.rocket.chat" with your server's name

i didn't find any recurrence of "open.rocket.chat" in my config.json any help plzzzzz

intissar12:
The value "open.rocket.chat" matches the default value, explained in Step 1.

  1. Add servername as suggested by the app: "open.rocket.chat", do not enter any credentials there.

The workaround was just a try & success :) It may help if your remove the config.json file and start over.
But not sure.

oppps my bad thx you man

unfortunatly it does not work. Our Server runs on port 8080
Does not work

Was this page helpful?
0 / 5 - 0 ratings

Related issues

SQUIDwarrior picture SQUIDwarrior  路  3Comments

Sugaroverdose picture Sugaroverdose  路  3Comments

engelgabriel picture engelgabriel  路  5Comments

paulz1 picture paulz1  路  3Comments

geekgonecrazy picture geekgonecrazy  路  4Comments