RocketChat
application gui keeps crashing
i have logged into the application many times and it keeps crashing. is there something specific i need to have on my computer in order for it to work and run? do i need to have a special video app or service? how do i keep it from crashing?
pls send the images of this issue that your are facing so then i can solve only
Having the same issue for days now. Not able to log in on Rocket.chat. Tried reloading the App, disabling GPU, restarting the App, re-installing it. Nothing works. Happens with Windows and macOS. Even on Safari/Firefox. Using the latest version of the App 3.9.11. Keep getting this screen. Username and passwords are correct since the error for bad credentials is different.
Also tried the workaround changing the OS language to english. Doesn't work as well.
Hello @azevedo-joao @tashalee991 can you open the browser devtools and check the console for any errors? Thanks!
Yes, I will check.
On Mon, Jan 22, 2024 at 6:55 AM Martin Schoeler @.***> wrote:
Hello @azevedo-joao https://github.com/azevedo-joao @tashalee991 https://github.com/tashalee991 can you open the browser devtools https://rocket.chat/docs/contributing/reporting-issues#gathering-logs and check the console for any errors? Thanks!
— Reply to this email directly, view it on GitHub https://github.com/RocketChat/Rocket.Chat/issues/31504#issuecomment-1904053329, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFPYBPJ4TH7GLMC66PA2PPTYPZVTPAVCNFSM6AAAAABCDQKVWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUGA2TGMZSHE . You are receiving this because you were mentioned.Message ID: @.***>
Hello @azevedo-joao @tashalee991 can you open the browser devtools and check the console for any errors? Thanks!
made this one on Google Chrome on macOS, tried to log in in a incognito window. Do you need more info or is this enough?
Hi, any chance you could include the required information from the issue template? It is very important for us to debug issues. Mainly for this case it would be really nice to now the server version and if there's any specific login settings that were changed (configured OAuth, Ldap, password policy, etc).
Thanks for reporting the issue, I'm waiting on your response.
Hi, any chance you could include the required information from the issue template? It is very important for us to debug issues. Mainly for this case it would be really nice to now the server version and if there's any specific login settings that were changed (configured OAuth, Ldap, password policy, etc).
Thanks for reporting the issue, I'm waiting on your response.
Hi, in the case of @azevedo-joao it is the snap installation version 6.5.2 on Ubuntu 22 LTS: Version: 6.5.2 Deployment ID: Qv4RERTtmkYyeFJXn Apps Engine Version: 1.41.0 Node Version: v14.21.2 Database Migration: 304 (January 23, 2024 10:18 PM) MongoDB: 5.0.15 / wiredTiger (oplog Enabled)
Login is configured with LDAP. Since the login works for all other users now and worked for him until a couple of days, there can't be a misconfiguration in that.
We have now another user that gets the same GUI-error: Application Error The application GUI just crashed.
His developer console says:
SDKClient.ts:86 r {isClientSafe: true, error: 'not-allowed', reason: undefined, details: undefined, message: '[not-allowed]', …}details: undefinederror: "not-allowed"errorType: "Meteor.Error"isClientSafe: truemessage: "[not-allowed]"reason: undefinedstack: "Error: [not-allowed]\n at n (https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:178:18922)\n at w._livedata_nosub (https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:178:18994)\n at w.onMessage (https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:178:21749)\n at https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:148:2678\n at Array.forEach (
I never got the app to work. It just connected through website
On Wed, Jan 24, 2024, 6:43 AM Nissulya @.***> wrote:
Hi, any chance you could include the required information from the issue template? It is very important for us to debug issues. Mainly for this case it would be really nice to now the server version and if there's any specific login settings that were changed (configured OAuth, Ldap, password policy, etc).
Thanks for reporting the issue, I'm waiting on your response.
Hi, in the case of @azevedo-joao https://github.com/azevedo-joao it is the snap installation version 6.5.2: Version: 6.5.2 Deployment ID: Qv4RERTtmkYyeFJXn Apps Engine Version: 1.41.0 Node Version: v14.21.2 Database Migration: 304 (January 23, 2024 10:18 PM) MongoDB: 5.0.15 / wiredTiger (oplog Enabled)
— Reply to this email directly, view it on GitHub https://github.com/RocketChat/Rocket.Chat/issues/31504#issuecomment-1908149949, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFPYBPJ5TCBM4GSAB7FXWODYQEFYHAVCNFSM6AAAAABCDQKVWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYGE2DSOJUHE . You are receiving this because you were mentioned.Message ID: @.***>
Hello! I've been encoutering the same problem with the exact same error in console. Has a solution been found?
For our user there was a problem with a change in his ldap attributes. His first name was changed to a double name and this produced the error that the user couldn't be mapped to the existing user (we map our user on attributes mail, sn and givenName). Also a change of the name (=givenName+sn) and of the mail in the mongodb didn't helped to map the existing user properly. We had to rename/remove the existing user and he got a new user after a new login.
I never got the app to work. I just did it online
On Mon, Feb 5, 2024, 3:05 AM Nissulya @.***> wrote:
For our user there was a problem with a change in his ldap attributes. His first name was changed to a double name and this produced the error that the user couldn't be mapped to the existing user. We map our user on attributes mail, sn and givenName. Also a change of the name (=givenName+sn) of the mail in the mongodb didn't helped to map the existing user properly. We had to rename/remove the existing user and he got a new user after a new login.
— Reply to this email directly, view it on GitHub https://github.com/RocketChat/Rocket.Chat/issues/31504#issuecomment-1926620925, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFPYBPMYCYWT3N3LYGZV2B3YSCVHDAVCNFSM6AAAAABCDQKVWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRWGYZDAOJSGU . You are receiving this because you were mentioned.Message ID: @.***>
Hi, any chance you could include the required information from the issue template? It is very important for us to debug issues. Mainly for this case it would be really nice to now the server version and if there's any specific login settings that were changed (configured OAuth, Ldap, password policy, etc). Thanks for reporting the issue, I'm waiting on your response.
Hi, in the case of @azevedo-joao it is the snap installation version 6.5.2 on Ubuntu 22 LTS: Version: 6.5.2 Deployment ID: Qv4RERTtmkYyeFJXn Apps Engine Version: 1.41.0 Node Version: v14.21.2 Database Migration: 304 (January 23, 2024 10:18 PM) MongoDB: 5.0.15 / wiredTiger (oplog Enabled)
Login is configured with LDAP. Since the login works for all other users now and worked for him until a couple of days, there can't be a misconfiguration in that.
We have now another user that gets the same GUI-error: Application Error The application GUI just crashed.
His developer console says:
SDKClient.ts:86 r {isClientSafe: true, error: 'not-allowed', reason: undefined, details: undefined, message: '[not-allowed]', …}details: undefinederror: "not-allowed"errorType: "Meteor.Error"isClientSafe: truemessage: "[not-allowed]"reason: undefinedstack: "Error: [not-allowed]\n at n (https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:178:18922)\n%5Cn) at w._livedata_nosub (https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:178:18994)\n%5Cn) at w.onMessage (https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:178:21749)\n%5Cn) at https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:148:2678\n at Array.forEach ()\n at c.forEachCallback (https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:148:3735)\n%5Cn) at socket.onmessage (https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:148:2648)\n%5Cn) at r.dispatchEvent (https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:148:8437)\n%5Cn) at https://chat..../a15638969a6bc86bf0be09bd08fe964f16c367e5.js?meteor_js_resource=true:148:18870\n at Array.forEach ()"[[Prototype]]: Error _define_property.mjs:14 TypeError: Cannot destructure property 'type' of 'j[e]' as it is undefined. at eval (LoginForm.js:1:4366) at B (LoginForm.js:1:4457) at sv (_define_property.mjs:14:1) at s7 (_define_property.mjs:14:1) at ey (_define_property.mjs:14:1) at cJ (_define_property.mjs:14:1) at cX (_define_property.mjs:14:1) at cQ (_define_property.mjs:14:1) at c$ (_define_property.mjs:14:1) at _define_property.mjs:14:1
Have same issue with exactly same errors in browser console
In the case of joao there was also a change in the spelling of his name in ldap ( "ã" changed to "a") and although we changed the name (=givenName+sn), username und the ldap "importIds" : to "CN=Azevedo\, Joao etc. rocketchat still refused to map him to the existing user on login and throws the error: 'errorClass","message":"Username already exists. [403]","stack":"Error: Username already exists'. I suspect, this is because of the ldap-id:
"ldap" : { "id" : "417a657665646f2c204a6fc3a36f20284241503435393029", "idAttribute" : "name" }, because it seems to be built from the name attribute, but I don't know how exactly this id is built