Cloudron Forum

Hello @phneutre Where does the 9595 port come from? Cloudron uses port 995 for pop3 according to https://docs.cloudron.io/email#pop3

Hello @admo Please write a mail to support@cloudron.io and enable remote support, see https://docs.cloudron.io/support so wen can have a look.

Hello @david-0 @David-0 said: Is that even possible? No and maybe yes. Let me be blunt. Nextcloud does not make it easy for you to switch users from one provider to another. There is: https://apps.nextcloud.com/apps/user_migration but I doubt it does what you need. I have done this once but for LDAP to local user and did write down the steps I took. So this might work the same way for OIDC users, but the SQL queries need to be altered acordingly. Nextcloud LDAP to Local User Migration Yes, it is possible, but each user must then be assigned a password. This can be done manually or scripted. Post: https://help.nextcloud.com/t/import-ldap-users-get-rid-of-ldap/56629/11 commands used: Enable Maintenance mode sudo -u www-data php -f /app/code/occ maintenance:mode --on Users that will see a change of login id after the process SELECT * FROM oc_ldap_user_mapping WHERE owncloud_name != directory_uuid; Name clashes between normal and LDAP users. SELECT uid FROM oc_users, oc_ldap_user_mapping WHERE owncloud_name=uid; Name clashes between normal and LDAP groups SELECT gid FROM oc_groups, oc_ldap_group_mapping WHERE gid = owncloud_name; Create one normal user per LDAP user. INSERT INTO oc_users (uid, uid_lower) SELECT owncloud_name, owncloud_name FROM oc_ldap_user_mapping; Create on normal group per LDAP group. INSERT INTO oc_groups (gid) SELECT owncloud_name FROM oc_ldap_group_mapping; Disable the user_ldap app sudo -u www-data php -f /app/code/occ app:disable user_ldap Remove LDAP user bindings. DELETE FROM oc_ldap_user_mapping; Remove LDAP group bindings DELETE FROM oc_ldap_group_mapping; Remove LDAP group memberships DELETE FROM oc_ldap_group_membership; Disable Maintenance mode sudo -u www-data php -f /app/code/occ maintenance:mode --off

Hello @aaaaargzombies @aaaaargZombies said: TLDR I'm on version 9.0.17 and should try upgrading. Yes, you should update to Cloudron 9.1.3 for cloudron install to work without the need to build and push the image before installing.

Hello @themeerkat I have added your package to the list: https://forum.cloudron.io/topic/15172/community-apps

@james said: If you find something unclear of lacking in the documentation ... Just getting my head around the workflow, and I like to "spell things out" : build the Community App (previously known as a Custom App) (my 'old fashioned' approach : docker build, docker push, cloudron install, probably keep doing that because my build script does it, don't fix what ain't broke) make a CloudronVersions.json file same folder as project dev folder (Dockerfile, start.sh, CloudronManifest.json, README.md, POSTINSTALL.md etc.) cloudron versions init cloudron versions add maybe add to my build script why "CloudronVersions" in the plural ? I guess Cloudron thinking is that a Community App might have v1.0.0, v1.0.1, v2.0.0 Very complete approach, lovely but with cloudron versions revoke I wonder if this will ever be in true in practice (I would likely revoke every old version). upload CloudronVersions.json to static hosting gotcha but if I have 10 Custom oops Community Apps, what is Cloudron team envisioning : that I will have 10 Surfer apps (app1.tim.uk, app2.tim.uk, etc) ? Or 1 sectioned Surfer app (communityapps.tim.uk) ? Or no Surfer apps and just stick CloudronVersions.json in the relevant git repo (urls to files from git are not always clear) ? I guess you probably don't care, but I'm intrigued what your expectations are Cloudron CLI help typo ? % cloudron versions --help Usage: cloudron-versions [options] [command] Hyphenated ?

Reopening this. I suggested this in the community app topic here. @robi suggested this may now be possible to address. My suggestion was this: I'd love to see RSSBridge packaged in a way that you could update individual bridges directly from their repo. The official Cloudron app has the bridges in a read only folder. Lots of bridges are updated constantly, while the main app seems to be working without much problems. So as a consequence we don't get the fixed bridges on Cloudron, leading to more and more broken bridges, but with the app itself working as it should.

@robi said: @odie the package can be adjusted to fix that.. just ask the team by creating a separate post for it I did a while ago but it wasn't implemented. I can try again my previous suggestion, I can post again in this thread Sorry for hijacking this topic. I will not post more about this in this topic.

@girish @Joseph n8n team are claiming the issue could be with changes made by Cloudron between 2.9.4 and above. Can you guys look into this? There are multiple people claiming that sending binaries via multi-part-forms breaks after upgrading from 2.9.4 - but I don't know if they're using Cloudron. Here's an example of someone getting the same error sending a multi-part form using the Open AI file upload: https://github.com/n8n-io/n8n/issues/26777 Other references to connection issues when uploading files: https://github.com/n8n-io/n8n/issues/26746 https://github.com/n8n-io/n8n/issues/26606 https://github.com/n8n-io/n8n/issues/25567

It sounds like this app could use a reverse proxy with a user editable configuration so the routes and ports can be added manually.

@jypelle this is possible if the package is adjusted to have the config file available in /app/data and a script to restart/reload the relevant service.

@girish said: What I meant is maybe the manifest can use "postgreSQL": { "prefixCount": 10 } and it creates 10 databases or something like that. I like this approach. How would you handle changes with this count though, say it's 10 today but lowered to 5 tomorrow? Surely that'd be a breaking change. Otherwise, I think it'd be the easiest solution