Errors [error-invalid-user] and [error-invalid-room] #22256
Comments
|
Anton, Can you edit that to say REST not REAT ? |
Done! |
|
Hi, I have also observe this EDIT: |
|
I can reproduce this error....
Steps to reproduce:
|
|
Actually any time a user opens a DM window with another user for the first time, this exception seems to occur. Not just when you click on the user from the directory page as I mentioned above. |
|
We are having this error too but I can't reproduce everytime, it seems to happen randomly when you want to send a DM to a user for the first time. Server Setup Information:
Client Setup Information
Additional contextREST API is enabled but I don't know if this is relevant. Only way to have access to RC again is to refresh the page/application (CTRL+R). Relevant logs: |
|
Still exist in 3.16.3 |
|
At 3.16.3 I see a lot of these: |
|
My guess, that all that invalid-room and invalid-user could be related to #21237 |
In my case I'm 100% sure that it have nothing to do with disabled users; the issue appears with active users. |
Can you share you experience in that problem? |
|
Same issue here : fresh Debian machine, fresh install RC 3.16.3 and Keycloack OpenID connect |
Please check my previous message: #22256 (comment) Unfortunately I don't have any way to reproduce :| |
|
Same with LDAP auth backend on another fresh install (not done by me furthermore). It's working well when LDAP was not connected. |
|
We have the same problem but we use OAuth2 for SSO. Every user that start a pm to a use he never spoke before, the invalid user pops up and requires a refresh. That sounds like not a big deal, but if the target audience is not tech affine this is rather deal breaking because a core function is just not working. We have this problem at least since 3.14.x, it got worse with 3.15 if I remember correctly. |
Encountering the same problem on our system. Steps to reproduce:
Expected behavior:A direct message channel is opened for the two users. Actual behavior:A grey screen appears with an error message in the top right corner: After refreshing the page the direct message channel is displayed correctly. Server Setup Information:Version of Rocket.Chat Server: 3.16.3 Client Setup InformationDesktop App: 3.2.3 Additional InformationLDAP Backend Authentication (Active Directory) is enabled. Relevant logs:Further informationThe following requests are being logged in Chrome Dev Tools: Afterwards, the grey screen and the error "Invalid User" are appearing. Tried to disable LDAP, but the error persists. |
|
Exactly the same error. RC Log: Chrome Dev Console: Also after refreshing (F5) with the {ROCKET_URL}/direct/ it works and opens the correct direct message channel. |
Guys, the PR related and tests I ran are considering the cases when opening a single DM or multiple DM for the first time. If there's a different behavior please let me know or open another issue. Thanks a lot! |
That's all actually still an issue on most recent 4.4.0 |
|
I have version 4.4.1 and the issue still persists. It does Not show "invalid user" error, but page refresh is required yet. |
|
Still an Error in 3.18.5. |
|
Reopening to investigate! |
Hey, @dougfabris Douglas! But to upgrade I need to wait a proxy fix #25022 |
|
Getting crash when switching frequently between rooms or search for a user that you don't have an active direct conversation with. Server: Docker 4.4.0 Use REST instead of websocket for Meteor calls disabled DevTools errors: |
Fixed in recent versions (4.5.2 I guess) |
Thank you! After update server to latest 4.6.2 problem when "search for a user" is not reproduced anymore! But unfortunately |
|
|
I am experiencing a similar issue on 4.8.3, though it is intermittent Steps to Reproduce:
Expected Behavior:add the new room without error or give a more precise explanation as to why it could not send the message Actual BehaviorRoom is added, no message is in the room, and an error is thrown (when using the web interface, "Error Not Allowed" shows up in red error bubble in the top right of the screen). Server Setup Information:
Client Setup Information:
Additional context
Relevant Logs:
|
|
we are on 5.3.5 now a I still get some invalid user and room errors |
|
@ankar84 and @calebjacobson have you added any temporary handling mechanism? I need to run an experiment using RocketChat and cannot wait for it to be fixed. |
|
I have the same problem: I use version |
|
Same issue on v |
Description:
Since I enabled Use REST instead of websocket for Meteor calls in Admin UI - General - REAT API (and I don't know why it was disabled, because default seems to be enabled state) I get in logs a lot of useless entries like this:
They a really useless because don't give information how to fix them - they don't mention which user or room is currently invalid. But instead of mention user or room it shows useless stack trace which is flooding our logs because we using docker deployment and that traces generates a lot of log entries.
Steps to reproduce:
Expected behavior:
Or clean logs or mention what user or room is invalid actually to handle that and fix it.
Actual behavior:
Flooded logs and (maybe) bad influence to server general load which could lead to instability.
Server Setup Information:
Client Setup Information
Additional context
Could be related to #21182 in stability aspect
Relevant logs:
The text was updated successfully, but these errors were encountered: