SolvedRocket.Chat [BUG] Users can't send messages (>= 2.4.x)

Description:

I updated from 2.3.2 to 2.4.0 - now regular users (only user role) can't send messages anymore. As bot or admin I still can send messages. Will roll back for now.

Server Setup Information:

  • Version of Rocket.Chat Server: 2.4.0
  • Operating System: Linux x64
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog: On
  • NodeJS Version: 8.17.0
  • MongoDB Version: 4.0.13

Relevant logs:

I20191228-13:33:45.469(1) server.js:204 System ➔ error Error sending message: Error: You are not authorized to change message properties
     at validateUserIdentity (app/lib/server/functions/sendMessage.js:164:9)
     at sendMessage (app/lib/server/functions/sendMessage.js:174:2)
     at MethodInvocation.sendMessage (app/lib/server/methods/sendMessage.js:86:11)
     at MethodInvocation.methodsMap.(anonymous function) (app/lib/server/lib/debug.js:67:34)
     at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1771:12)
     at DDP._CurrentMethodInvocation.withValue (packages/ddp-server/livedata_server.js:719:19)
     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1234:12)
     at DDPServer._CurrentWriteFence.withValue (packages/ddp-server/livedata_server.js:717:46)
     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1234:12)
     at Promise (packages/ddp-server/livedata_server.js:715:46)
     at new Promise (<anonymous>)
     at Session.method (packages/ddp-server/livedata_server.js:689:23)
     at packages/ddp-server/livedata_server.js:559:43 
44 Answers

✔️Accepted Answer

Same issue here.
Worked around it by using the reset feature in /admin/Message

image

Other Answers:

Hey folks. We are aware of this. We are working to fix it and release soon.

Changing the "set username to alias" setting to false Is indeed the workaround to solve this issue. You can still use the real name setting.

@jbguerraz Thanks! Resetting Message settings fixed our issue too.

The offending setting seems to be:
Screenshot from 2019-12-30 16-40-02
When it is enabled, the users cannot send messages. When it is disabled (default) they can.

Why I had this enabled probably stems from that I thought it would have something to do with the
Admin -> Layout -> User Interface -> Use Real Name
setting.

this has been fixed on the just launched version 2.4.3

More Issues: