Cloudron Forum

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 : [image: 1679341157587-c09bd926-0b5e-4850-8e26-b9413779a021-image-resized.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.

Hardened node developer here : long story short, nothing to worry about. NPM security warnings are completely broken, they have a near 100% false positive rate (technically, the "vulnerable" dependency is here, but the flaw is, in literally all instances I have seen, not exploitable). An interesting read about this if you want : https://overreacted.io/npm-audit-broken-by-design/

Thanks @girish

@atridad yes it does. If you run cloudron --help you can see the "global" options on the top, which apply also to subcommands.

@d19dotca this is now implemented at https://git.cloudron.io/cloudron/cloudron-cli/-/commit/e321442cc2251f46b0ee2564138224015339b12d and will thus be part of next cli release.

@nebulon said in Cloudron CLI login command results in an HTTP 404 error with "Cannot POST /api/v1/developer/login" message: You probably have to update the cli tool, since the /api/v1/developer/login route was long deprecated and finally removed from the server side. @girish said in Cloudron CLI login command results in an HTTP 404 error with "Cannot POST /api/v1/developer/login" message: For reference, the latest CLI version is 4.12.8 (Use cloudron --version to see current version) So I checked the version of Cloudron CLI finally and it seems I am indeed running 4.12.8... <username>@<computerName> ~ % cloudron --version 4.12.8 However, I ran the command cloudron login again and now it suddenly works. So I'm not sure, maybe I had ran the update (I know I did for a fact) but perhaps it wasn't recognized until my computer had restarted over the holidays here. Something strange, but it's all good now it seems.

I have pushed a new CLI version v4.12.7 that fixes this.

@christiaan I submitted a new image to the marketplace. Will leave a note here when it gets approved. Sometimes it's immediate and sometimes it takes 2-3 days.

For anyone else coming later, if you need to modify these files to test out for instance a code fix you would use the CLI tool to run cloudron debug --app app.domain.com, open a web terminal to the app, edit whatever files you need to in /app/code, and then run /app/pkg/start.sh from within that web terminal to manually start the app and test your change. You can exit debug mode, which will delete your changes, by going to the app's settings in cloudron, Repair, and clicking the Disable Recovery Mode button.