-
Notifications
You must be signed in to change notification settings - Fork 93
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
Connection refused when attempting to register user with CA #9
Comments
Hello @rgronback, First of all sorry for the late response. Could you share the services and the resources used? I think that the fabric-ca server is not exposed through the node port. |
Hello! No apologies necessary, thanks for the reply. To reproduce, I did the following starting with Kubernetes cluster reset on local Docker for Desktop on the Mac:
kind: StorageClass
Here is some detail, let me know if you need anything else: rgronback@deadwood hlf-operator % kubectl hlf ca register --name=org1-ca --user=peer --secret=peerpw --type=peer rgronback@deadwood hlf-operator % k logs -f org1-ca-6c487bc47f-m5vg5
rgronback@deadwood hlf-operator % k describe service org1-ca rgronback@deadwood hlf-operator % k describe pod org1-ca-6c487bc47f-m5vg5
Conditions: Warning FailedScheduling 11m (x4 over 13m) default-scheduler 0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims. rgronback@deadwood hlf-operator % k describe service istio-ingressgateway -n istio-system |
Hi @rgronback , it should work in the latest release, try updating. If the problem arises again, open the issue or contact me directly, thanks :) |
i have the problem when attempting to register user with CA. i get the following logg
|
Hi @zhangfuli Can you confirm if you have access to this IP: 192.168.65.4? The Kubectl plugin tries to access the URL <KUBERNETES_NODE>:<CA_NODE_PORT> so if you don't have access to the nodes in the Kubernetes cluster, or the IP is internal the Kubectl plugin won't work for you. |
My k8s cluster is also on local Docker for Desktop on the Mac. Here is some detail.
|
Hi @zhangfuli Can you try to access https://192.168.65.4:32408/cainfo from your MacBook? This issue's due to no connection from the machine where you're running the commands and your Kubernetes cluster. Also, in the same terminal you're running the enrol command, try to run the following scripts: curl https://192.168.65.4:32408/cainfo -k If it doesn't respond immediately, we can confirm that this error is because of no connectivity to the Kubernetes cluster. |
thank you a lot. i cannot access https://192.168.65.4:32408/cainfo. but i can access localhost:32408/cainfo. i will troubleshoot problems with my cluster |
Hello, I am using Kind for the cluster, and then when executing the following command. Did I miss something? Do I have to do something or setting on Docker desktop? Please shed some light on this. thank you kubectl hlf ca register --name=org1-ca --user=peer [fabsdk/fab] 2022/10/29 16:38:20 UTC - n/a -> INFO TLS Enabled |
The error is because the port is not open. |
Launching network "tradereboot": |
All went well until this point, received this response. Any help would be appreciated.
I also noticed the CA values.yaml was completely commented-out. Intentional?
2021/02/28 07:20:30 [INFO] TLS Enabled
2021/02/28 07:20:30 [INFO] generating key: &{A:ecdsa S:256}
2021/02/28 07:20:30 [INFO] encoded CSR
Error: POST failure of request: POST https://192.168.65.3:30180/enroll
{"hosts":["mbp.lan"],"certificate_request":"-----BEGIN CERTIFICATE REQUEST-----\nMIIBQzCB6gIBADBeMQswCQYDVQQGEwJVUzEXMBUGA1UECBMOTm9ydGggQ2Fyb2xp\nbmExFDASBgNVBAoTC0h5cGVybGVkZ2VyMQ8wDQYDVQQLEwZGYWJyaWMxDzANBgNV\nBAMTBmVucm9sbDBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABMzl5juvHE6cNI3J\ncqb51SpVhhj7IDvqARyO4ZbKI4G3bF12+uB/ablYX3W6pD6rgQ0V6HZitUa4pOPF\n9UwdI46gKjAoBgkqhkiG9w0BCQ4xGzAZMBcGA1UdEQQQMA6CDGRlYWR3b29kLmxh\nbjAKBggqhkjOPQQDAgNIADBFAiEA2pGQ462xdmt1h6X5ecLBUYmNVkPuHYDTcBfb\nBanocoUCIDNPLvA4ZqTFdcsTtr7vOhZLZyMCpsm7EgDZbaUwiFui\n-----END CERTIFICATE REQUEST-----\n","profile":"","crl_override":"","label":"","NotBefore":"0001-01-01T00:00:00Z","NotAfter":"0001-01-01T00:00:00Z","CAName":"ca"}: Post "https://192.168.65.3:30180/enroll": dial tcp 192.168.65.3:30180: connect: connection refused
The text was updated successfully, but these errors were encountered: