RocketChat / RocketChat/Rocket.Chat
Cannot login to RocketChat local server with any (non-web) client
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Steps to reproduce:
Any attempt to login from client app:
Expected behavior?:
Expected behavior:
easy login, as it does from several other devices and browsers.
Actual behavior:
(a terminating '/' is added to Server URL entry - odd?) "No valid server found at the URL."
Server Setup Information:
- Version of Rocket.Chat Server: 1.3.2
OS Type: linux
platform/arch: arm
OS Release: 5.4.72-v7+
Node version: v8.11.4
Mongo Version: 3.2.15
Mongo Storage Engine: mmapv1
Client Setup Information
- Desktop App or Browser Version: App version 3.0.3
- Operating System: Either MacOS 10.16 or Ubuntu 20.1 - same behavior
Additional context
Easily reproduced: Any attempt to log in from any RocketShare client (Electron?)
This is a local test server only - for the time being - so it has not been https-secured.
server pings - not a network issue
in fact, connection from browser to same server : AOK.
significant?: Have just updated Ubuntu to 20.10 - from 20.04
rocketchat-desktop has been removed and re-installed...
Relevant logs:
Server logs nothing at point of attempted login (from the Rocket client)
Relevant errors and other log output: logs show no evidence of login attempt...
Version of Rocket.Chat Server: 1.3.2
Server Setup Information: Fresh arm4f install on Raspberry PI (same behavior seen against Ubuntu install)
Our server address is http://192.168.42.78:3000 (local network test only, for the moment)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the login attempt in Rocket.Chat App 3.0.3 against the local HTTP server at http://192.168.42.78:3000, comparing it with browser access. Start by checking the desktop client’s server URL handling and login request, then verify that the client accepts the server and that the server records a login attempt without adding an invalid trailing slash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, node.js, typescript
- Domain
- authentication, desktop, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100