Registration Bug #32359
Comments
|
Thanks Scott for reporting this issue. Per our discussion we'll look into it. @geekgonecrazy - Do you know if this is a known issue that is being addressed by the team? It impacts the completion of registration and associated provisioning of starter license, access to cloud services, etc. |
|
Any details about the host running on? Any logs? Can you reproduce with log level increased? Can add environment variable: OVERWRITE_SETTING_Log_Level=2 to turn log level all the way up. If you can see anything even timeouts. Also from host if you can make sure can hit cloud.rocket.chat and it resolve? |
|
I had the experience with both snap and docker. I recreated another docker instance and enabled the additional logging. This is the log all the way and up to the "awaiting confirmation" page. Please note, the grey box with the security code is always blank on this first attempt and an email is never sent. If I hit "change email" and put in the exact same email address i used initially it then refreshes with a security code and I receive an email. Also, on the docker host, cloud.rocket.chat resolves to 34.230.175.106 Please let me know if you need anything else. (node:1) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023. |
|
any way you can paste the logs cleaner? Thats so long it'd take me forever to parse through and see whats going on. Looks like maybe grabbing through some aws tool instead of direct from logs? Maybe thats messing up formatting? THe logs directly out shouldn't be that badly formatted |
|
@geekgonecrazy at a guess: CloudWorkspaceRegistrationError: Workspace is not registered at Ports look mismatched, and Site URL using http too ? |
|
I'm traveling this week but will look again when back. Given it was to be
used internally, I didn't bother updating the host name. It is still
interesting error handling that it goes through after selecting change
email.
I'll let you know how it goes.
Thanks!
Scott
…On Wed, May 8, 2024, 7:19 AM John Crisp ***@***.***> wrote:
@geekgonecrazy <https://github.com/geekgonecrazy> at a guess:
CloudWorkspaceRegistrationError: Workspace is not registered at
Workspace does not have a valid access token, sync aborted
| Rocket.Chat Version: 6.7.2 |
| NodeJS Version: 14.21.3 - x64 |
| MongoDB Version: 6.0.15 |
| MongoDB Engine: wiredTiger |
| Platform: linux |
| Process Port: 3000 |
| Site URL: http://your-domain.com:3300 |
| ReplicaSet OpLog: Enabled |
| Commit Hash: cb97723 |
Ports look mismatched, and Site URL using http too ?
—
Reply to this email directly, view it on GitHub
<#32359 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AL553RHZBYSODGYOMPUETP3ZBIX7PAVCNFSM6AAAAABHCQBGLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQGY4TOMRVGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This issue has been marked as stale because there has been no further activity in the last 10 days. If the issue remains stale for the next 4 days (a total of 14 days with no activity), then it will be assumed that the question has been resolved and the issue will be automatically closed. |
github-actions
bot
added
the
stat: no response
|
This issue was closed because it has been inactive for 14 days since being marked as stale. |
!--
Please see our guide for opening issues: https://developer.rocket.chat/rocket.chat/contribute-to-rocket.chat/ways-to-contribute/report-bugs
If you have questions or are looking for help/support please see: https://rocket.chat/docs/getting-support
If you are experiencing a bug please search our issues to be sure it is not already present: https://github.com/RocketChat/Rocket.Chat/issues
-->
Description:
Upon registration, during the email verification page, the security code is blank. Additionally, no email is sent to the entered address. At this point, if i click change email and put in the exact same address as I put in initally, it behaves properly, sends the email and presents a code.
Steps to reproduce:
Expected behavior:
Email sent with security code.
Actual behavior:
No code, no email. Please see screenshot.
Server Setup Information:
Client Setup Information
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered: