@girish Sorry for the late and no reply. It was a new server with nothing on it, so it was just best for me to spend a couple of minutes and just reinstall everything. That worked. I know it doesn't help solve the problem, but that worked for me.

@jdaviescoates
by default yes, but there is an option to support IRC

@nebulon Yes, I did open a thread on the Rocketchat forum, I'll update there too.

Thanks for your help on this.

@opensourced I tried this on Android.

I thought registering the server in the initial setup screen made things work but it didn't. What I had to do was:

Administration -> Connectivity Services . On top right, click Cloud console:
c00b8bb4-526f-469d-a67e-cf784d3438bb-image.png

Then, I registered a new account there with my email. Verified the email. I then created a selfhosted instances to got a "token" which I had to put in the UI above.

After that, I Administration -> Push and clicked on Send a test push to my user . That did not work.

Restarted the app

Administration -> Push and clicked on Send a test push to my user . That worked. I got This is a push test message notification.

I just did a test and our app package has the same issue as mentioned in the links you posted.

@girish Good shout, and thank you kindly.

So frustrating to see features removed unnecessarily.

@fiwand @BrutalBirdie I have pushed a new package that auto-creates admin user and disables open registration by default. This change is only for new installations, existing ones are untouched.

One thing is that previous packages used to disable password change for users (when using LDAP). But now, I had to allow it because otherwise admin user cannot change it. Hopefully, that's an ok compromise.

@digitegal If you post it, they will come.

I have pushed the update to 4.0.1

I have pushed an update to 4.0 now. We will roll it out slowly, just to make sure there are no major breakages. The list of LDAP changes are at https://docs.rocket.chat/quick-start/identity-management-ee-vs-ce#ldap3 . Overall, it seems that LDAP filter, basic sync etc are all there in CE.

@jdaviescoates Oooh, ok. that might be it.

I was using my user account. Ok. Ill try making a bot account.

Thank you.

Found an issue: MongoDB needed up 600Mb of RAM (to be adjusted in services page).

@fbartels Thank you, that was it! In case anyone else finds this blog post, the updated instructions are here: https://docs.cloudron.io/apps/#custom-csp

@marcusquinn Good catch, I have disabled it for the next package release. https://git.cloudron.io/cloudron/rocketchat-app/-/commit/3b90cf6a9a79209bce455d33044c322892dfb3aa

@fbartels Hmmmm - might need to rethink my change there then too - why can't life just be simpler! 🙄

Thanks for the thought and link.

@girish Ahhh, that makes sense. Yeah an info note is probably enough, since it's a one-time thing, and there's a LOT of settings in RC to scan otherwise.

@cleveradmin sure. https://git.cloudron.io/cloudron/rocketchat-app/ is the repo and https://git.cloudron.io/cloudron/rocketchat-app/-/blob/master/Dockerfile is the Dockerfile. If they want to test , they can also use the demo instance https://my.demo.cloudron.io (username: cloudron password: cloudron)

@onlybro same here. No problem with the ios rocket.chat app and rocket.chat on cloudron.

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.

21537c50-4cb1-4911-94c4-f16aac44b35e-image.png

@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.