Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Command line error handling needs some improvements

Command line error handling needs some improvements

Scheduled Pinned Locked Moved Solved Support
2 Posts 2 Posters 358 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Robin
    wrote on last edited by
    #1

    I haven't used the command line tool for a while. I tried to use it today, and was greeted with this: Failed to get apps: 401 message: No such token. Logging in again fixed it.

    I think this was an expired token, so it might be the 401 response is wrong. It would also be great if there was some handling/translation of the error codes on the cli side for user-friendliness.

    nebulonN 1 Reply Last reply
    1
    • R Robin

      I haven't used the command line tool for a while. I tried to use it today, and was greeted with this: Failed to get apps: 401 message: No such token. Logging in again fixed it.

      I think this was an expired token, so it might be the 401 response is wrong. It would also be great if there was some handling/translation of the error codes on the cli side for user-friendliness.

      nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      @robin pushed a commit to at least give some explanation for 401 https://git.cloudron.io/cloudron/cloudron-cli/-/commit/d90b23c8b561f29f444145d40e4097cb098e5fa1

      Apparently no token or invalid token provided to the REST api currently both returns 401.

      1 Reply Last reply
      2
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Bookmarks
      • Search