Cloudron Forum

Thank you!

@BrutalBirdie That should be part of the docs!

@affinity yes, everything that you see in the UI has a corresponding API call. The dashboard is a pure frontend app. Unfortunately the docs for the API are lacking but we have someone working on this actively.

For the moment, just look into the browser console for the API call it makes when cloning a application. Usually, it's a simple REST call.

cc : @lassgutsein

@darren if you hit any issues, feel free to ask here.

Thanks for the hint - trying that I got a more meaningful error notice. It was one of the ipdeny urls (IPv6 list for North Korea) that resulted in an empty HTML file, throwing off the ipfile format.

@girish Thanks, that was it.

via api you can do that.
POST
{{baseUrl}}/mail/:domain/mailboxes
note :domain is a variable for the mail domain.
note {{baseUrl}} is the Cloudron api url e.g. https://my.DOMAIN.TLD/api/v1

with body:

{ "name": "webmaster", "ownerId": "uid-be9dcf57-ad65-40e0-a3f8-d1c75974bf01", "ownerType": "user" }

The ownerType can be user or group. and the ownerId you need to get via either /users and for groups /groups.

The API and the API Doc is currently being reworked.
https://git.cloudron.io/cloudron/docs/-/blob/master/api/cloudron_api_swagger.yaml?ref_type=heads

Thanks, everyone!

Good to know it should work. I will try it again later. Can't reboot now in the middle of the day. Maybe something got cached in the browser then.

@webvsnet Ah alright 🙂 Remember that when you upgrade Cloudron, you will have to get back to CLI 5.4.0

@girish said in Issue with the API to change MemoryLimit:

--data-raw '{"memoryLimit":973078528}

Thanks! this bit helped.

@girish thanks for pointing out to code.

As always:
In vino veritas - and in Source-Code

@nebulon, @BrutalBirdie
Thx to both of you, the call is now working.
curl -kX POST -H "Content-Type: application/json" https://my.smthg.com/api/v1/apps/install?access_token=857f7d7eb583cfb951e5a50c75a762b94304d4ba50d4a0c94950643eaab7959a -d '{"appStoreId": "io.n8n.cloudronapp@2.37.0","subdomain": "workflow","domain": "somethg.com","accessRestriction": {"users":[],"groups":[]}}'
{
"id": "c6c79d78-7c7c-414b-acf7-8b5cc39370ed",
"taskId": "269"
}

It needed obviously the header, but also I thought reading the API specs that accessRestriction could be null. It is not the case, so I used @BrutalBirdie assignment (empty users and groups) and the call succeeded.
Once again thank you very much.

Ignore me. This was an issue with PowerShell apparently. If run from linux it works fine.

Thanks again

@girish well, that solved the problem i was facing, though i do not understand why it does, but anyway, thanks a lot that helped me 😌 ✌

Solved!!
Solution = <Just sign in to the app store in your Cloudron Server as Mr. @girish said>

Once more, thank you very much for the support 😃 .

Glad you managed to resolve this. Some ago we changed the REST api there which probably caused this issue when using an outdated cloudron cli tool.

@girish said in Some problems with API - PUT user in groups:

{"groupIds":["gid-3e96c503-d30f-4db8-aa37-ecaf98fa33fa"]}

Thank you, works fine. It was a spelling-error in the "content-type" .

@girish sorry, a school boy mistake, the Content-Type header did the trick, but I made a typo in the backupId, that's why I got the error.

@robi @timconsidine good catch, I don't think it is. Will fix. Opened https://git.cloudron.io/cloudron/box/-/issues/832 to track internally

@plusone-nick
I didn't check the part of our code that manage user creation for ages, but 99% sure, that you don't need to provide a password, or not even a username just an email.

Then you create the invite link with a second request if you want to have the onboarding process managed by cloudron.

Personal note:
Remember that as the server owner you are responsible for the content hosted in it, for this is normally a good idea to have some manual approval before creating an account from a form; or you have to provide a good moderation.