-
Notifications
You must be signed in to change notification settings - Fork 38
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
Certificate is valid for ingress.local, not test-network-org0-ca-ca.localho.st error on network up #105
Comments
Hi @charalarg ./network up is compatible with rancher desktop and k3s. However - the What is happening above is that the CA client is trying to connect to the cluster ingress at port 443, and hitting the Traefik controller that has been installed with Rancher Desktop. Basically - you have two ingress systems running, both trying to bind to :80 and :443. Quick fix for this is to disable the Traefik ingress in the Rancher Desktop settings. OR to change the ingress port bindings in the Using the Nginx config that comes with the ./network up script is probably the easiest path forward. The other alternative would be to enable the ssl-passthrough mode for Traefik. There are some notes on Rancher setup in the samples project at https://github.com/hyperledger/fabric-samples/blob/main/test-network-k8s/docs/KUBERNETES.md#rancher-desktop-and-k3s |
Hello @jkneubuh, |
I managed to run the ingress successfully by disabling the other one occupying the ports but then i get another error.
Maybe this is not relevant but something seems broken to my network config. |
Is anyone else having this error message on
./network up
?I am running a local cluster with rancher desktop and k3s.
This error comes up when enrolling org0 root CA admin rcaadmin:
Debug logs:
The text was updated successfully, but these errors were encountered: