Skip to content

Failed to register user in CA for peers #261

@rishi-imentus

Description

@rishi-imentus

What happened?

I am having a kubeadm kubernetes cluster on my VM's with 1 master and 3 worker and i am trying to deploy fabric network with bevel-fabric-operator . I am following exact same procedure of README but after Deploy a certificate authority when i try to register user in CA for peers i am getting "Error: POST failure of request: POST https://org1-ca.localho.st:443/enroll
{"hosts":null,"certificate_request":"-----BEGIN CERTIFICATE REQUEST-----\nMIHzMIGbAgEAMBExDzANBgNVBAMTBmVucm9sbDBZMBMGByqGSM49AgEGCCqGSM49\nAwEHA0IABBmvk92Xc/ltuhK91ENwKPYi7CX9OurrW/hyr3y/f1vuVZDpJzfUlUs9\n3gSKAWxS3wt8hurq6VAf4csv/TaZ0sWgKDAmBgkqhkiG9w0BCQ4xGTAXMBUGA1Ud\nEQQOMAyCCms4cy1tYXN0ZXIwCgYIKoZIzj0EAwIDRwAwRAIgK9vUvIRSsitxzSKr\nDnSBbFYrwHrUzJOIZVK3KymXsmYCIAE07VyYBSjse132P+GWcEEyXzIaptvHH5fp\nLJAPZcyl\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://org1-ca.localho.st:443/enroll": dial tcp [::1]:443: connect: connection refused" and with the curl command i am getting "curl -k https://org1-ca.localho.st:443/cainfo
curl: (7) Failed to connect to org1-ca.localho.st port 443 after 0 ms: Couldn't connect to server" . I am running commands from my master node . When i try this in kind cluster everything works fine without any changes but it is not working in kubeadm cluster . Is there any particular doc that i can follow to deploy fabric on kubernets for production level

What did you expect to happen?

it should work properly and run without any error

How can we reproduce it (as minimally and precisely as possible)?

as minimally and precisely as possible

Anything else we need to know?

For storage class i am using ceph storage which is perfectly integrated with kubernetes . And i dind change anything in istios gatway and on DNS files , i am using them as it is .

Kubernetes version

Details
# kubectl get nodes -o wide

root@k8s-master:# kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
k8s-master Ready control-plane 26d v1.30.11 192.168.0.35 Ubuntu 24.04.2 LTS 6.8.0-58-generic containerd://1.7.27
k8s-worker-2 Ready worker 11d v1.30.12 192.168.0.33 Ubuntu 24.04.2 LTS 6.8.0-58-generic containerd://1.7.27
k8s-worker-3 Ready worker 26d v1.30.11 192.168.0.144 Ubuntu 24.04.2 LTS 6.8.0-58-generic containerd://1.7.27
root@k8s-master:
#

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions