-
-
Notifications
You must be signed in to change notification settings - Fork 14
-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating Hetzner robot admin sub-account fails (2019) #32
Comments
@basvandijk: Geesh, thanks for the report... will fix that until tomorrow. |
Great! Please let me know how I can help. |
@basvandijk: Hm, for all of my robot accounts this works... Did you by chance enable 2FA? |
No 2FA is not enabled. One thing I did do differently when ordering a new server was choosing to log into the rescue system using my public key instead of via a password but I don't think this matters for logging into the robot interface. |
@basvandijk: Can you check whether the |
Hi, colleague here. When making a new attempt to provision the device mentioned in the OP I hit the same issue. The The fact that this works probably means the environment variables nix-shell -E 'with (import ./.); myEnvFun { name = "nixops"; buildInputs = [ nixops nix ]; }' --run 'nixops deploy -s MyState.nixops -d stalling-net --include MyDevice' The running in a nix shell was added by @basvandijk to run Nixops HEAD (as mentioned in the OP), but it's extremely likely that either our Haskell shake tool or the Nix shell fail to pass the environment variables. I've found that running an The machine is provisioned now, making it hard to test, but it seems more than likely that the issue was on our side. As such I think the issue can be closed. @basvandijk Do you agree? |
@FPtje workaround does not work for me. It does not make any difference wether I defiene robot user and pass in the nix file or in the environment. Is there any progress in solving this issue? |
the hetznerctl tool does not work for me as well, I tracked the problem down to https://github.com/aszlig/hetzner/blob/master/hetzner/robot.py#L173 , it seems the server does not set the expected cookie. Maybe hetzner changed there api? |
@flicaflow: This is a different issue than the one reported here, but you're right, Hetzner now uses a CSRF token. |
@basvandijk: Given @FPtje's comment, can this be closed? |
@aszlig like in NixOS/nixops#778 it looks like Hetzner has changed its login mechanism again:
This is with the nixops from release-18.09. If I try it with nixops-HEAD (NixOS/nixops@330094b) and hetzner-HEAD (aszlig/hetzner@0df67db) I get the following failure:
The text was updated successfully, but these errors were encountered: