You only need what in NFS is described when you use NFS: https://docs.cloudron.io/volumes/#nfs

@GluttonStone ah thanks, maybe there was an issue in the server+client version mismatch then.

@nebulon Just popping back here to say this worked a charm, thanks!

@Grienauer Is the calls port enabled? It's the location UI . Default port is 8443 . This should also be opened up in the firewall.

it worked, thanks @joseph !

@joseph fixed with the latest update. Thank you!

@wnstfy What is mm package version? Maybe your bug is also solved with https://forum.cloudron.io/topic/12611/error-loading-users-with-latest-mm-update

Might be a good idea to disable automatic updates for the app if you don't want Mattermost 10 . But we have no idea how long MM 9 will continue to be supported.

@vadim thank you very much

Thanks for the tip, I have entered it there: https://forum.mattermost.com/t/online-offline-status-indicator-in-the-mac-app-broken/19481/3

@djxx oh wow, thanks for the detailed write up! Hopefully it's useful for other people migrating as well. I will add a link to your report from our docs.

Connect to postgres like this (replace the variables below with the ones you put in pgloader): export PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE}

@Lanhild Sorry missed your message. I will see if I can do another test migration this afternoon (CEST) and take some more notes. But basically I wrote the steps below on a clean Mattermost PostgreSQL install: Dumped the DB with : pg_dump -d mattermost > mattermost.dump Renamed on cloudron config.json to config.json.orig Copied mattermost.dump and config.json to cloudron mattermost via the file manager Edited config.json with the value from config.json.orig (to get the PostgreSQL details) "ServiceSettings" => "SiteURL" "SqlSettings" => "DataSource" and "DataSourceReplicas" "FileSettings" => "Directory" From the terminal app did PASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} pg_restore -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} ../data/mattermost.dump Rsynced all my attachments from origin_server to cloudron_server:app_folder (cf girish post ) Restarted the app

You can run the CLI tool on Cloudron like https://docs.cloudron.io/apps/mattermost/#command-line-tool . Instead of the import command at https://docs.cloudron.io/apps/mattermost/#migration , use the export command. To get a file off Cloudron, easiest way is to export to a path under /app/data and then use the File manager to download it. I am also curious why you are not able to update mattermost on Cloudron. It's all automatic.

@CBCUN It was an incorrect passkey in my case. Using the correct one worked.

@cvachery yeah, I encountered the same (had to reset passwords post migration etc). Might be worth reporting upstream.

@alexis Thanks for sharing the instructions but instead of copying files directly to /home/yellowtent/appsdata/xxx , you should use the File Manager .

Glad this got sorted

Very strange, i tried again with another method. When i untar the file on my computer (ubuntu desktop) first and i send the directory with cloudron file manager and change the directory ownership, i have an error on activation and it does't work. When i send the targz file directly and extract it with the file manager and change the ownership all is ok and it works ! @girish is it normal ? Problem solved