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


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
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

Cloudron Forum

Apps | Demo | Docs | Install

CLI Not accepting server

Scheduled Pinned Locked Moved Solved Surfer
14 Posts 5 Posters 412 Views
    • 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.
  • ? Offline
    ? Offline
    A Former User
    wrote on last edited by A Former User
    #1

    I run a deploy step for surfer in my GitLab CI, and it seems to now be failing to put the files. I get the following error:
    d825202c-2557-4715-96bc-271fd8474fba-image.png

    Any ideas if this was something to do with a recent update @nebulon ?

    robiR 1 Reply Last reply
    0
  • robiR Offline
    robiR Offline
    robi
    replied to A Former User on last edited by robi
    #2

    @atrilahiji did you validate the variables are present in the environment? And does surfer login work manually?

    Life of sky tech

    ? 2 Replies Last reply
    0
  • ? Offline
    ? Offline
    A Former User
    replied to robi on last edited by
    #3

    @robi Checking to make sure it actually works but I didn't change anything in my CI setup. Might actually be a GitLab issue if thats the case.

    1 Reply Last reply
    0
  • ? Offline
    ? Offline
    A Former User
    wrote on last edited by
    #4

    Didn't seem to matter. Weird part is I can run this locally just fine πŸ˜•

    Also I tried printing out the API key just before the surfer put call and it looks correct.

    fbartelsF 1 Reply Last reply
    0
  • ? Offline
    ? Offline
    A Former User
    replied to robi on last edited by A Former User
    #5

    Nevermind... it seems like this is an issue with a newer release. When logged out, I get the message in my screenshot above. When logged out, it works.

    Why would one need to be logged in when they are using an API key? Doesn't make a lot of sense to me...

    robiR 1 Reply Last reply
    0
  • robiR Offline
    robiR Offline
    robi
    replied to A Former User on last edited by
    #6

    @atrilahiji means the API key doens't work πŸ˜‰

    something for @nebulon to take a peek at

    Life of sky tech

    1 Reply Last reply
    0
  • fbartelsF Offline
    fbartelsF Offline
    fbartels App Dev
    replied to A Former User on last edited by
    #7

    @atrilahiji said in CLI Not accepting server:

    Also I tried printing out the API key just before the surfer put call and it looks correct.

    Did you also check the variable that holds the server url?

    ? 1 Reply Last reply
    0
  • nebulonN Online
    nebulonN Online
    nebulon Staff
    wrote on last edited by
    #8

    Which version is the cli ? I've released a new version yesterday with updated dependencies and the updated commandline argument parser required fixes, maybe I missed some there.

    ? 1 Reply Last reply
    0
  • ? Offline
    ? Offline
    A Former User
    replied to nebulon on last edited by
    #9

    @nebulon it’s the latest version. I don’t specify a version in my computer and I only got the error on my desktop when I updated

    1 Reply Last reply
    0
  • ? Offline
    ? Offline
    A Former User
    replied to fbartels on last edited by
    #10

    @fbartels Yes and I can relplicate on the latest version with a hard coded URL

    1 Reply Last reply
    0
  • ? Offline
    ? Offline
    A Former User
    wrote on last edited by
    #11

    I realize there is a lot of work for 2 people to do, but I just figured I would ping here again as I imagine this may affect more people than just me. If it would help, I can try to look through the recent commits to see what could have caused this and propose an MR to resolve it.

    girishG 2 Replies Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to A Former User on last edited by
    #12

    @atrilahiji Let me see now if I can quickly find what broke. We use surfer for our docs.cloudron.io CI/CI as well pretty much like what you are doing. I wonder what's different.

    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to A Former User on last edited by
    #13

    @atrilahiji I can confirm the latest surfer is broken. As a workaround you can try to install cloudron-surfer@5.12.2 and that works.

    @nebulon Our docs builds fail now when it was updated from 5.12.2 to 5.13.5

    1 Reply Last reply
    0
  • nebulonN Online
    nebulonN Online
    nebulon Staff
    wrote on last edited by
    #14

    This should be fixed with the latest cli version cloudron-surfer@5.13.5-1
    This does NOT require an app update, just the cli

    1 Reply Last reply
    3

  • Login

  • Don't have an account? Register

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

  • Don't have an account? Register

  • Login or register to search.