I certainly feel it's right for us not to just complain but actively get involved with providing feedback and testing support for all the good work you do, and I look forward to hearing more about your plans and discovery of what works well for all those that care for your good product.
I gave this a try in the demo instance and I could upload a large file as well. @Mastadamus Can you check if you are able to reproduce this in our demo instance at https://my.demo.cloudron.io (username: cloudron password: cloudron). There's a bunch of large sample files that you can upload from this site - https://www.quinticsports.com/sample-videos/ . This will help us figure if this is related to browser or your network or your server etc.
Also, the error inside rocket.chat usually says the exact number like " File exceeds allowed size of 1 B. [error-file-too-large] ". Does it say 100MB in that error for you? That would mean the File Upload size setting did not get saved for some reason.
@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 🤷
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.
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).
@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.