Fresh install but stuck in "Provisioning"?

I want to start by saying I’m new to rancher and kubernetes. This project is my first and seeing as how it hasn’t worked out yet, I’m seeking help with little background knowledge of how this is supposed to work.

I was able to log into the front end and create a cluster but it’s stuck at “provisioning” with the following message below:
[etcd] Failed to bring up Etcd Plane: etcd cluster is unhealthy: hosts [10.0.1.105] failed to report healthy. Check etcd container logs on each host for more information

I have rancher 2x installed on ubuntu in vmware.
Docker version: 19.03.8
Host available memory >4G
I have installed rancher by the “2 easy steps” method from the website.

etcd log below and repeats:
2020-10-05 21:08:49.710986 I | embed: rejected connection from “10.0.1.105:36305” (error “EOF”, ServerName “”)
2020-10-05 21:08:50.858667 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-controller-manager" " with result “range_response_count:1 size:508” took too long (637.9387ms) to execute
2020-10-05 21:08:50.858871 W | etcdserver: read-only range request “key:”/registry/namespaces/default" " with result “range_response_count:1 size:258” took too long (134.642235ms) to execute
2020-10-05 21:08:53.154527 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-controller-manager" " with result “range_response_count:1 size:508” took too long (266.282303ms) to execute
2020-10-05 21:08:53.600789 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-scheduler" " with result “range_response_count:1 size:482” took too long (134.915336ms) to execute
2020-10-05 21:08:59.885016 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-scheduler" " with result “range_response_count:1 size:482” took too long (155.809755ms) to execute
2020-10-05 21:09:06.450499 I | embed: rejected connection from “10.0.1.105:38140” (error “tls: failed to verify client’s certificate: x509: certificate signed by unknown authority (possibly because of “crypto/rsa: verification error” while trying to verify candidate authority certificate “kube-ca”)”, ServerName “”)
2020-10-05 21:09:11.461309 I | embed: rejected connection from “10.0.1.105:38144” (error “tls: failed to verify client’s certificate: x509: certificate signed by unknown authority (possibly because of “crypto/rsa: verification error” while trying to verify candidate authority certificate “kube-ca”)”, ServerName “”)
2020-10-05 21:09:16.473422 I | embed: rejected connection from “10.0.1.105:38146” (error “tls: failed to verify client’s certificate: x509: certificate signed by unknown authority (possibly because of “crypto/rsa: verification error” while trying to verify candidate authority certificate “kube-ca”)”, ServerName “”)
2020-10-05 21:09:45.962599 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-controller-manager" " with result “range_response_count:1 size:509” took too long (486.54076ms) to execute
2020-10-05 21:09:48.217308 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-controller-manager" " with result “range_response_count:1 size:509” took too long (238.09574ms) to execute
2020-10-05 21:09:48.661761 W | etcdserver: read-only range request “key:”/registry/services/endpoints/kube-system/kube-scheduler" " with result “range_response_count:1 size:577” took too long (439.39869ms) to execute
2020-10-05 21:09:48.838515 I | embed: rejected connection from “10.0.1.105:36445” (error “EOF”, ServerName “”)
2020-10-05 21:09:50.935638 W | etcdserver: read-only range request “key:”/registry/namespaces/default" " with result “range_response_count:1 size:258” took too long (210.649988ms) to execute
2020-10-05 21:09:50.935673 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-scheduler" " with result “range_response_count:1 size:481” took too long (236.263423ms) to execute
2020-10-05 21:09:51.138066 W | etcdserver: read-only range request “key:”/registry/deployments" range_end:"/registry/deploymentt" count_only:true " with result “range_response_count:0 size:6” took too long (135.11026ms) to execute
2020-10-05 21:09:51.138203 W | etcdserver: read-only range request “key:”/registry/masterleases/10.0.1.105" " with result “range_response_count:1 size:134” took too long (198.245224ms) to execute
2020-10-05 21:09:52.497129 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-controller-manager" " with result “range_response_count:1 size:508” took too long (157.62514ms) to execute
2020-10-05 21:09:58.836456 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-controller-manager" " with result “range_response_count:1 size:509” took too long (222.631687ms) to execute
2020-10-05 21:10:01.063602 W | etcdserver: request “header:<ID:17535456696867379608 username:“system:node” auth_revision:1 > txn:<compare:<target:MOD key:”/registry/masterleases/10.0.1.105" mod_revision:228112 > success:<request_put:<key:"/registry/masterleases/10.0.1.105" value_size:66 lease:8312084660012603798 >> failure:<request_range:<key:"/registry/masterleases/10.0.1.105" > >>" with result “size:18” took too long (224.954592ms) to execute
2020-10-05 21:10:01.064067 W | etcdserver: read-only range request “key:”/registry/services/endpoints/kube-system/kube-controller-manager" " with result “range_response_count:1 size:604” took too long (221.579843ms) to execute
2020-10-05 21:10:03.320188 W | etcdserver: read-only range request “key:”/registry/services/endpoints/kube-system/kube-scheduler" " with result “range_response_count:1 size:577” took too long (177.417703ms) to execute
2020-10-05 21:10:03.320243 W | etcdserver: read-only range request “key:”/registry/leases/kube-system/kube-controller-manager" " with result “range_response_count:1 size:509” took too long (180.10481ms) to execute
2020-10-05 21:10:03.320311 W | etcdserver: read-only range request “key:”/registry/csidrivers" range_end:"/registry/csidrivert" count_only:true " with result “range_response_count:0 size:6” took too long (179.803915ms) to execute
2020-10-05 21:10:06.365274 I | embed: rejected connection from “10.0.1.105:38178” (error “tls: failed to verify client’s certificate: x509: certificate signed by unknown authority (possibly because of “crypto/rsa: verification error” while trying to verify candidate authority certificate “kube-ca”)”, ServerName “”)
2020-10-05 21:10:11.376947 I | embed: rejected connection from “10.0.1.105:38182” (error “tls: failed to verify client’s certificate: x509: certificate signed by unknown authority (possibly because of “crypto/rsa: verification error” while trying to verify candidate authority certificate “kube-ca”)”, ServerName “”)
2020-10-05 21:10:16.387466 I | embed: rejected connection from “10.0.1.105:38184” (error “tls: failed to verify client’s certificate: x509: certificate signed by unknown authority (possibly because of “crypto/rsa: verification error” while trying to verify candidate authority certificate “kube-ca”)”, ServerName “”)
2020-10-05 21:13:04.941879 I | mvcc: store.index: compact 227879
2020-10-05 21:13:04.943360 I | mvcc: finished scheduled compaction at 227879 (took 1.239471ms)

Hello,
I had the same problem, this is how I was able to solve it.,
through rancher web-ui / Culster / Edit Cluster: change the value of “Authorized Cluster Endpoint” at Disabled