@chymian-0 We saw the exact same problem with @robi's instance. Essentially, one of the plugins was preventing the startup. After the log line "Your Etherpad version is 1.8.12", one is supposed to see "http server listening" or something like that. I recommend "npm rm" on each of the plugins as suggested in https://docs.cloudron.io/apps/etherpad/#troubleshooting to debug which plugin causes this issue. Unfortunately, this is the life with plugins in etherpad, they keep breaking between releases

I will mark this as "solved" since etherpad in the Cloudron incarnation would not support this as is.

Since I just looked into this, the errors (or rather warnings) from npm are for one thing, that etherpad does not have a package.json file in the root folder, but relies on the node_modules folder for listing. Also npm by default attempts to check for update of itself, which fails and it should not update on its own, since we only test against specific versions. The vulnerabilities are indeed an issue, however as @girish mentioned we cannot blindly update them, so all those have to be ideally reported upstream with all the relevant plugins even.

@jdaviescoates nice, feels a lot more like gDocs, along with all the data collecting at the beginning..

@girish Thank you kindly

it works fine, sorry @girish I should have read the Etherpad Cloudron app doc and also the Ownpad one, because I have to enable the detection of pad mimetype by NextCloud https://github.com/otetard/ownpad/#mimetype-detection. In the terminal, I copied /app/code/resources/config/mimetypemapping.dist.json to /app/data/config/mimetypemapping.json and then I added in this file pad'': ["application/x-ownpad"], we could add this information to the Cloudron documentation of the NextCloud app, next time I'll read it