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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved CLI Not accepting server

    Surfer
    5
    14
    406
    Loading More Posts
    • 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.
    • ?
      A Former User last edited by A Former User

      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 ?

      robi 1 Reply Last reply Reply Quote 0
      • robi
        robi @Guest last edited by robi

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

        Life of Advanced Technology

        ? 2 Replies Last reply Reply Quote 0
        • ?
          A Former User @robi last edited by

          @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 Reply Quote 0
          • ?
            A Former User last edited by

            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.

            fbartels 1 Reply Last reply Reply Quote 0
            • ?
              A Former User @robi last edited by A Former User

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

              robi 1 Reply Last reply Reply Quote 0
              • robi
                robi @Guest last edited by

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

                something for @nebulon to take a peek at

                Life of Advanced Technology

                1 Reply Last reply Reply Quote 0
                • fbartels
                  fbartels App Dev @Guest last edited by

                  @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 Reply Quote 0
                  • nebulon
                    nebulon Staff last edited by

                    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 Reply Quote 0
                    • ?
                      A Former User @nebulon last edited by

                      @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 Reply Quote 0
                      • ?
                        A Former User @fbartels last edited by

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

                        1 Reply Last reply Reply Quote 0
                        • ?
                          A Former User last edited by

                          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.

                          girish 2 Replies Last reply Reply Quote 0
                          • girish
                            girish Staff @Guest last edited by

                            @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 Reply Quote 0
                            • girish
                              girish Staff @Guest last edited by

                              @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 Reply Quote 0
                              • nebulon
                                nebulon Staff last edited by

                                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 Reply Quote 3
                                • First post
                                  Last post
                                Powered by NodeBB