CLI Not accepting server
-
wrote on Jan 21, 2021, 8:01 PM last edited by A Former User Jan 21, 2021, 8:02 PM
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:
Any ideas if this was something to do with a recent update @nebulon ?
-
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:
Any ideas if this was something to do with a recent update @nebulon ?
wrote on Jan 21, 2021, 9:31 PM last edited by robi Jan 21, 2021, 9:32 PM@atrilahiji did you validate the variables are present in the environment? And does surfer login work manually?
-
@atrilahiji did you validate the variables are present in the environment? And does surfer login work manually?
wrote on Jan 21, 2021, 10:28 PM 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.
-
wrote on Jan 21, 2021, 10:50 PM 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.
-
@atrilahiji did you validate the variables are present in the environment? And does surfer login work manually?
wrote on Jan 21, 2021, 11:36 PM last edited by A Former User Jan 21, 2021, 11:39 PMNevermind... 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...
-
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...
-
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.
@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?
-
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.
wrote on Jan 22, 2021, 1:29 PM 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
-
@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?
wrote on Jan 22, 2021, 1:30 PM last edited by@fbartels Yes and I can relplicate on the latest version with a hard coded URL
-
wrote on Jan 23, 2021, 8:43 PM 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.
-
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.
@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.
-
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.
