@blaise ah ok, but yes I can see the same error message as such, but after revisiting the channel it seems to work fine. If that is what you mean, then this is very much an upstream bug. I did a quick search in their issue tracker, but couldn't find anything specific yet.

@blaise It heavily depends on the usage. 1.000 members without any interaction? 200 concurrent uses? Good news is: you can easily restore your whole Cloudron or a single app on a "bigger" instance. (just in case your vps provider can't do an upgrade of your vps). So the advice is: start with a smaller instance and throw some more cpu&ram on it in a later state with knowledge about the load.

Their bot didn't like whatever format I tried posting the issue on GitHub so after a 2nd attempt got auto-closed I just emailed their Zendesk. No clue why an open-source project would use Zendesk though

Can confirm. Switching channels is more reasonable now.

@parhelium I have published a new package 2.13.1. You can edit /app/data/env to add custom vars.

@derin Is the rocket.chat hosted on Cloudron as well? If so you have to set the CSP headers on the chat app to allow embedding - see https://docs.cloudron.io/apps/#custom-csp

@potemkin_ai It seems to appear fine in our chat instance atleast. I get a preview of the pdf as well. Do you see anything in the app logs? [image: 1610942873760-5df3896b-d0dc-49ae-9189-acd146af7d3f-image.png] Might be worthwhile testing with different pdfs as well. Maybe some specific pdfs have issue.

OK, this got sorted out. There is a domain allow list set inside Rocket.Chat. There was confusion on where a user's email address comes from. It comes from the Users view and not from the Email view. The email view is used only by the mail server.

@girish Yeah that was my takeaway as well. Hopefully it is polished soon on their end.

@privsec It seems if you send the request id to rocket.chat support, they can help you out . See https://github.com/RocketChat/Rocket.Chat/issues/19396#issuecomment-728653283 (Also, saw this same message on their forum - https://forums.rocket.chat/t/i-cant-connect-to-rocket-chat-cloud/9589).

Just to add, when I was setting this up I found the WordPress plugin didn't work, but the pasting code snippet did.

Will do, good to know it's not an issue on my end. Thanks for the quick reply!

Just in case: I've seen that https://github.com/RocketChat/Apps.GitHub, but it doesn't seem to be installable in docker configuration of Rocket.Chat

Yup, your story sums up my Cloudron experience. [image: 1597848844483-2988aeb5-9a88-4409-8585-d2e137e0fb26-bild.png]

@robw @alex-adestech An update on this. Crux of the issue is that the indices name generated are too long. @alex-adestech pointed out to me that this issue only sorted out in MongoDB 4.4 and not even MongoDB 4.2. Searching through the rocket.chat issue tracker I saw only person hit this and nobody replied. Search further, I found that Rocket.Chat doesn't even support MongoDB 4.2. The releases page mentions the versions they test with - https://github.com/RocketChat/Rocket.Chat/releases. This got me wondering why we hit this issue. Well, the answer it turns out is that Cloudron generates 32 byte mongodb database names for apps. This in turn ends up affecting the length of the index. I have made a fix now for Cloudron 5.6 that generates shorter names. (We have had to do something similar for apps using MySQL as well in the past).

Pushed a new package

@girish Ah yes, sorry. Should've looked. At least maybe this will direct someone to the docs if they end up here again.

@YurkshireLad The memory recommendation is the absolute minimum memory below which the app won't run reliably. Like even with 1 user, it won't run properly below that recommendation. The amount of memory required to host 100 users... is hard to know. Usually, the answer to this depends on the how all these users user Rocket.Chat. If they use simultaneously and if they use it from multiple devices etc. Cloudron will give you a notification (email) if an app is running out of memory. So, you can just take it slow and increase the app's memory limit as you go. You can also look into the upstream project's memory recommendation for 100 users.