# Waiting for API to be available

**URL:** <https://forums.suse.com/t/waiting-for-api-to-be-available/12258>\
**Category:** SUSE Rancher Prime\
**Created:** [November 6, 2018, 12:43am UTC](https://forums.suse.com/t/waiting-for-api-to-be-available/12258 "2018-11-06T00:43:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Josh\_H](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@Josh\_H](https://forums.suse.com/u/Josh_H)\
**Post date:** [November 6, 2018, 12:43am UTC](https://forums.suse.com/t/waiting-for-api-to-be-available/12258/1 "2018-11-06T00:43:24Z")

</div>

so we have a rancher cluster that was lost in a DR test which we are trying to restore however after several days we still cannot get it running again with identical config, 3 masters and 3 nodes.

running RKE v0.1.9 on an azure stack we have tried the following.

1. cleaning out all remaining certs and pruning the docker system.

2. redeploying the entire cluster.

3. recreating the config file.

however the issue still persists where the APIserver is not available.

We have found some errors but nothing obvious, how would we begin to troubleshoot ?

the main one we have found in the kube-apiserver logs is

```auto
http: TLS handshake error from abc:13758

```

but we cant get any clear idea of why the server is unavailable of the certs are generated cleanly.

What causes this ?? were kind of in a bind as we need this environment for other operations.