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. Surfer
  3. [CLI] put command no longer working: invalid token

[CLI] put command no longer working: invalid token

Scheduled Pinned Locked Moved Unsolved Surfer
2 Posts 2 Posters 42 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.
    • D Offline
      D Offline
      dhornbein
      wrote last edited by dhornbein
      #1

      Hello, I'm using the CLI to deploy a site via CI/CD. After the 6.4.1 update it seems that something has broken in the put cli command.

      surfer get --token <token> --server https://protocol.ecologies.info /
      works as expected

      surfer put --token <token> --server https://protocol.ecologies.info / test.txt /
      gives an error of invalid token

      I've tried new tokens to no avail. I've tested on my local machine which reproduces the problem in the build.

      Our CI system worked as expected April 30th before the update, but after the 6.4.1 update our build system began to fail with the invalid token

      We rolled back the cloudron surfer server to 6.4.0 and it appears to be working again.

      Any help would be greatly appreciated, thank you

      1 Reply Last reply
      0
      • nebulonN Away
        nebulonN Away
        nebulon
        Staff
        wrote last edited by
        #2

        I can't quite see how anything between those versions could have affected this and especially since reverting the app will put the old app back anyways, the only issue may come from the cli then or the token actually be invalid.

        To rule out one bit also, is the SSL certificate valid for the app?

        Also do you see any error in the server side app logs and can you use the cli outside your CI/CD?

        1 Reply Last reply
        0
        • nebulonN nebulon marked this topic as a question
        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