New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web access connection problems since upgrade 4.6.3 -> 4.7.0 #25460
Comments
I have been running some tests on my site again the last few days, but with no progress. For example, I manually disabled the Content Security Policy in MongoDB, but this only resulted in the disappearance of the corresponding console output - the main problem still persists. I think that connection problem is caused by not finding the module "stream". Is there any way to check that the module is present in Docker? Is there perhaps a setting that bypasses the module? Or maybe it is possible to load the module manually? |
New findings on my part: The error is still existing in Rocket.Chat 4.7.1 and 4.7.2. The error seems to lie within the mongo database. When I export the database and import it in a new docker enviroment, the error occurs. If I setup a new clean database with Rocket.Chat 4.6.3 (and do some test channels, messages), migrate to 4.7.0 or above, the error does not occur. I can provide the mongo database (~ 400 MB) via private message, if needed. And last, but not least: There's a similar issue listed in meteor: meteor/meteor#11974, which is fixed in meteor-node-stubs package version 1.2.3. But I couldn't get my Docker environment to use the new version yet (it uses version 1.2.1). |
New findings in my part 2: The error is still existing in Rocket.Chat 4.8.0-rc.0. Also, I tried to fix this bug myself by building Rocket.Chat with NodeJS 4.19.1/meteor 2.7.2/meteor-node-stubs 1.2.3 on Ubuntu 22.04 and imported my mongodb - the bug doesn't occur here anymore and the web access works fine again. But now I'm stuck creating an pull request out of my findings.
|
@sampaiodiego Hey, Diego! Please consider to test linked PR and if possible include that in 4.8 release. |
* Bumb meteoer-node-stubs to version 1.2.3 to fix issue #25460 * yarn.lock Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>
* Bumb meteoer-node-stubs to version 1.2.3 to fix issue #25460 * yarn.lock Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>
closed by #25669 |
Description:
Web access is not available due to connection problems, but the Rocket.Chat App launches and is usable through Android apps (cannot test it with iOS). The web parts of the android apps (e.g. Admin Panel) doesn't load either.
The error occurred after the upgrade from 4.6.3 to 4.7.0 with the docker image.
Steps to reproduce:
Expected behavior:
Rocket.Chat should greet me with a functional login screen.
Actual behavior:
The login screen doesn't load completely, and a connection banner on the top of screen appears (see screenshot). This behavior occurs in Edge, Chrome and Firefox (no other browsers tested).
Server Setup Information:
Client Setup Information
Additional context
I tried to roll back to Rocket.Chat version 4.6.3 (docker), but this version doesn't start anymore due to "migration 261 not found".
Relevant logs:
Rocket.Chat Startup-Log:
docker --version
ldd --version
Firefox console messages (other browsers are similar):
The text was updated successfully, but these errors were encountered: