Cloudron Forum

@marcusquinn I like this project and just wanted to get it a bump

Hi,
for debugging purposes, we need GUI access to the nextcloud prostgres db on Cloudron. However, this is causing some trouble. We set up a lamp server and uploaded phpPGadmin. In the pgadmin config, we set postgres as the server host.

Now, when we try to log in, we get the message "sign-in failed". Postgres logs don't show a login attempt.

Is there any proven way to get this working?

Okay, I got it fixed now; rebooting did the trick with redis.
For those who come along with this thread:

I guess when used on machines with many CPU-Cores, especially with hyperhreading, OnlyOffice starts some kind of worker per Core, which then eats up some memory. In my case, with 16 cores (32 HT-Cores), this eats about 3.25 Gbytes. If the memory limit is too low, this results in a restart loop. Since I resized the memory to 6 GB, all is fine.

Hi,

the auto provisioning of the LDAP-Sync of Freescout works like a charm. Nevertheless I would suggest that ldap sync is limited to the elegible groups which are selected within Cloudron.

This would require the field DNs and Filters within Freescout to be set to a value like the following instead of the default:

ou=users,dc=cloudron(memberof=cn=GROUPNAME,ou=groups,dc=cloudron)
ou=users,dc=cloudron(memberof=cn=GROUPNAME,ou=groups,dc=cloudron)

At this point it comes in handy that freescout accepts multiple lines of filters, so there can be one line for each group selected within the Cloudron backend.

This change is needed for the following reasons:

• Cloudron overwrites this setting from time to time – so it cant' be changes manually.
• Reduction of attack surface – if only a small part of an organization needs the ticket system not everybody should have an account. Mind authenticated exploits.
• Order: Many unneeded Users within Freescout make it confusing.

I would be happy if one feels like implementing this

Hi!

I migrated a Wordpress site from a old server to Cloudron. I did this by copying the wp-content folder, importing the db (which I cleared before) and writing the secrets to wp-config.conf.

Everything works like a charm except e-mail. Wordpress just is not able to send out e-mails. There's nothing in the logs – neither the app-logs nor the mailserver log. So the mail does not even reach the cloudron mailserver.

There is no funky custom smtp plugin installed. I just think that there are some special cloudron e-mail-configs for wordpress which do not restore after restart and are not documented (at least I am unable to find such) to apply manually.

Mail on other apps works fine.

@girish I can confirm, we are using the EE Version. So this might be a bug in the OnlyOffice EE-Version not Cloudron?

Hi Folks!

I wonder if anyone of you got Mattermost Team Edition to work with the Cloudron OIDC-Provider. I currently run a setup where I use Keycloak with Mattermost, but I want to replace it with cloudron – Mattermost-Support is currently the only dealstopper.

If I recall right, the issue with using the GitLab auth feature with any other OIDC IdP was that Mattermost Team Edition expects a claim "id", which needs to be an integer and unique to the user – and also be added to the userinfo.

As far as I can see currently, Cloudron does not support such a token and therefore can't be used with Mattermost Team Edition.

I know that Mattermost EE has a more broad support of sign-in methods. However, in these special circumstances, it is not an option because I have a high number of occasional users, which would render using Mattermost EE a financial disaster.

Mabe one of you have some wise thoughts on this. Thank you in advance!

@girish said in LDAP Integration: Limit sync to groups selected in cloudron:

@im-fabian said in LDAP Integration: Limit sync to groups selected in cloudron:

Nevertheless I would suggest that ldap sync is limited to the elegible groups which are selected within Cloudron.

This should already be the case.

Thanks, I can confirm this behaviour!

I see that this is not a cloudron issue but a freescout one: Users which have been deleted within LDAP are not locked or deleted within freescout but just remain in the status of their latest sync.

@girish I opened an ticket with OnlyOffice on that cause. Will keep you posted.

@girish I am on the Team Edition. Indeed OpenID in a restricted manner is available, but it is designed to work with the default gitlab configuration only: https://docs.mattermost.com/onboard/sso-gitlab.html
There is nothing in the license which forbids to use this auth-endpoint for other purposes. Additionally you can change the text and color of the login button via the config.json.

A tutorial for keycloak can be found here: https://medium.com/@mrtcve/mattermost-teams-edition-replacing-gitlab-sso-with-keycloak-dabf13ebb99e

@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