Cloudron Forum

@im-fabian does using the psql command directly work? That will help us debug if this is mistake in postgres credentials or some pgadmin issue.

@nebulon that solves the problem. Thx.

I totally get the warning, however: due to budget restraints I have to do it that way. 🙂

@girish thx, that solved the problem. Problem was that during migration I replaced the whole wp-content-folder with the folder from the instance I migrated.

@girish the support replied. I did not have the time to look into it, but wanted to share the feedback with you asap:

You are correct, but you can decrease the amount of converter processes by changing maxprocesscount parameter in default.json file: /etc/onlyoffice/documentserver/default.json "FileConverter": { "converter": { "maxprocesscount": 1, The default value is "1" but you can change it (to 0.5 or 0.25 for instance) to decrease the number of processes, since maxprocesscount is a multiplier, the number of converter processes will be equal to maxprocesscount * number of CPUs. Please, do not forget to restart Document Server's services after applying the changes: supervisorctl restart all

@im-fabian I think that behavior is fairly common in all apps. When users get removed from a directory, they don't get removed in the app itself on a sync. This is because there may be data specific to the user and (for the app) it's not clear what needs to be done . For example, maybe freescout has some tickets assigned to a delete user. What should it do? Assign to someone else/orphan them etc.

@girish that would be great. Could provide Cloudron SSO for Mattermost out of the box.

For unique integer: We used the field employeenumber in ldap and just let the ldap server count one up per each user added.