@girish So i did actually set it to zero before and commented out the nginx file path. So that killed it. IN THE PAST But setting the upload to 0MB in the config and restarted. It actually worked. Wow! Thanks for having a functioning forum and the speedy response!

Not sure if this is related but in the logs for Surfer, which I have as a redirect for the root domain, I am getting a 404 for the matrix .well-known constantly. GET /.well-known/matrix/client 404 1.083 ms - 328 Were you ever able to look into this @girish?

@nebulon Thanks. Will try it.

Rename to Element and update pushed.

That went well, I have pushed an update.

Locking this, please see other topic.

@danigl As you probably know, the port 8448 is only for server <-> server communication. What port are you using for server <-> client communication? In Cloudron package, we use the same port for server <-> server and client <-> server communication (which is port 443).

@xavierl I have pushed a new version of synapse that allows matrix to manage it's own users. If you re-install synapse, you will see this option.

@xavierl You practically can. Just grant no Cloudron users access to it while also enabling open registration in the Matrix app internal settings.

@girish I needed it to be able to properly federate with other Matrix servers. Like I said, it was pretty weird.

@scooke No problem It's quite confusing because I have been leaving various bits of progress all over this forum in various places... Just to give an update on the current status. I have gotten synapse published. I put some initial docs at https://cloudron.io/documentation/apps/synapse/ (reading that now, there seems to a big wall of text. I have to simplify it). I am publishing riot now. But both the apps require Cloudron 5.1.4 which is now going through our CI. In 5.1.4, we have a way to add .well-known docs which is required for synapse/riot to work. Hopefully, we should be in a releasable state tomorrow.

@scooke https://git.cloudron.io/msbt/matrix-riot-app is the repo you want to use. Follow instructions in the documentation on how to install the CLI and how to build and install custom apps.