Cloudron Forum

Ah, thanks! I hadn't seen the app-mail-folders before. 🙂

@girish Thank you, Girish!
After I updated the node, this error went away.

@luckow good catch. In fact, the sort function usage was entirely wrong.

Fixed in https://git.cloudron.io/cloudron/cloudron-cli/-/commit/87dcb5f8cc8ae29f877a6f5b96c865ec48dd8846

I published a new CLI 5.5.0

Solution is to install the Cloudron CLI in a container, LAMP App or Surfer App work well.

See: https://forum.cloudron.io/topic/10966/installing-custom-apps-on-cloudron/

Got it, thanks!

Ok got it, thanks @BrutalBirdie ! No problem with doc being overhauled, I understand it's a WIP; just wanted to make sure it's not me that can't properly RTFM 🙂

Please check if it's any better with CLI 5.4.1

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

Thank you 🙂

Ok. I will doublecheck this. Give me a few hours for this.
Thanks for the moment 🙂

Update: Solution work fine! Thanks a lot. 👍

@nebulon said in Cloudron CLI:

ah. The cli is actually not built to run on Cloudron itself, but it would interact with a Cloudron via REST api.

Is there a specific use-case where you need it on the server?

I want to install the InfluxDB Package, I thought then via Cloudron CLI. So I have to install it on my Client, to install this package.

@scooke I am out of ideas then. If you like, you can reach out on support@cloudron.io and we can debug further to see if we can resurrect the app.

Found https://rsync.samba.narkive.com/DFt4GEa9/over-stdin-stdout which has some interesting discussion.

@girish Sure for test domains w/o any subdomains.

What I'm suggesting is a non-entirely blocking situation when the automation fails what it thinks it needs with no simple recourse.

Would improve UX flow in edge cases..

This can be set to solved !

Cloudflare reply :

c09bd926-0b5e-4850-8e26-b9413779a021-image.png

@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.

@nebulon thanks

@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.