-
I don't know what I'm doing wrong, but these buttons are greyed out on all my hosts. My roles all have |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 9 replies
-
Beta Was this translation helpful? Give feedback.
-
I have disabled session MFA (in case it was the culprit), did not help. I did notice the following error in the logs, though, directly after connecting:
calling |
Beta Was this translation helpful? Give feedback.
-
I managed to figure out what I was doing wrong, and it was quite a doozy: my node resource has a metadata.name field, in the form of this field has a very surprising behaviour:
|
Beta Was this translation helpful? Give feedback.
I managed to figure out what I was doing wrong, and it was quite a doozy: my node resource has a metadata.name field, in the form of
hostname:port
. i am generating them from a script/template, and pipe them straight intotctl create -f
(which uses the metadata.name to match up which host i am updating).this field has a very surprising behaviour:
hostname:port
, web ssh itself works, but upload/download is broken (this might be related to the "unable to resolve hostname" error i posted above)