You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting an error which is enroll failed: enroll failed: POST failure of request: POST https://xx.xx.xx.xx:31931/enroll {"hosts":null,"certificate_request":"-----BEGIN CERTIFICATE REQUEST-----\nMIH3MIGfAgEAMBeeeeeeeeBMGByqGSM49AgEGCCqGSM49\nAwEHA0IABJkaVaotjYa3gO1Gm02VDEeiUbedgus0HKJ12xqV7a+Pu5CNNN60jNEG\nAZEpGLV9RvZu0iNnYGToH+HRCs1PJ+qgLDAqBgkqhkiG9w0BCQ4xHTAbMBkGA1Ud\nEQQSMBCCDmRvY2tlci1kZXNrdG9wMAoGCCqGSM49BAMCA0cAMEQCIAEo5t2PqeeeeeeeeTtbiJ7JQDifDDeOOCuv16AiB1ZuIjlIQ/WaylWWmh5gLTcbm3Yyzb\nGS7+9+tbIxUV1g==\n-----END CERTIFICATE REQUEST-----\n","profile":"","crl_override":"","label":"","NotBefore":"0001-01-01T00:00:00Z","NotAfter":"0001-01-01T00:00:00Z","ReturnPrecert":false,"CAName":""}: Post "https://xx.xx.xx.xx:31931/enroll": x509: certificate is valid for 127.0.0.1, xx.xx.xx.xx, not xx.xx.xx
Could anyone please tell me if our cert is stored on any server at first run and we can't access the new cert on new IP or any other issue?
The text was updated successfully, but these errors were encountered:
Currently, I'm building a network on Kubernetes using this repo. there were 2 worker nodes. I set up a Kube config file of AWS EKS.
When I run the command :
Getting an error which is
enroll failed: enroll failed: POST failure of request: POST https://xx.xx.xx.xx:31931/enroll
{"hosts":null,"certificate_request":"-----BEGIN CERTIFICATE REQUEST-----\nMIH3MIGfAgEAMBeeeeeeeeBMGByqGSM49AgEGCCqGSM49\nAwEHA0IABJkaVaotjYa3gO1Gm02VDEeiUbedgus0HKJ12xqV7a+Pu5CNNN60jNEG\nAZEpGLV9RvZu0iNnYGToH+HRCs1PJ+qgLDAqBgkqhkiG9w0BCQ4xHTAbMBkGA1Ud\nEQQSMBCCDmRvY2tlci1kZXNrdG9wMAoGCCqGSM49BAMCA0cAMEQCIAEo5t2PqeeeeeeeeTtbiJ7JQDifDDeOOCuv16AiB1ZuIjlIQ/WaylWWmh5gLTcbm3Yyzb\nGS7+9+tbIxUV1g==\n-----END CERTIFICATE REQUEST-----\n","profile":"","crl_override":"","label":"","NotBefore":"0001-01-01T00:00:00Z","NotAfter":"0001-01-01T00:00:00Z","ReturnPrecert":false,"CAName":""}: Post "https://xx.xx.xx.xx:31931/enroll": x509: certificate is valid for 127.0.0.1, xx.xx.xx.xx, not xx.xx.xxCould anyone please tell me if our cert is stored on any server at first run and we can't access the new cert on new IP or any other issue?
The text was updated successfully, but these errors were encountered: