> For the complete documentation index, see [llms.txt](https://help.gopaddle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gopaddle.io/troubleshooting/cluster-resource-view-issues/network-error-servererror-response-not-successful-received-status-code-503.md).

# Network Error ! ServerError: Response not successful: Received status code 503

### Scenario

Viewing the resources under a cluster, may fail with error.  <mark style="color:red;">**Network Error !**</mark> <mark style="color:red;"></mark><mark style="color:red;">ServerError: Response not successful: Received status code 503</mark>. This happens when you try to view the cluster resources immediately after registering the Cluster in gopaddle.

<figure><img src="/files/z8ob4oaslejRuPhdym0d" alt=""><figcaption><p><strong>Network Error !</strong> ServerError: Response not successful: Received status code 503</p></figcaption></figure>

### Solution

###

1. Navigate to the cluster Home folder.
2. Under the **Installed Add Ons** section, verify if the **kubeagent-server** is listed.

<figure><img src="/files/eZmWfwRCBx2Kq1F5l9z8" alt=""><figcaption></figcaption></figure>

3. Click on cluster **Refresh** option to refresh the discovered resources

<figure><img src="https://lh7-us.googleusercontent.com/E6aFPXycWyCsSeBSZLOggdAnDas6A_Rm2K5QOleJZwOomHb5b4LvTy5_IeEueShZ5jQQJIigYHf_ZFrk0L6UJ0_CK60Np8Twe-yvEL7Xj1Bc4Ax0un2G369Uy7X9KZuVToAYN0NeBd-ZGKgyj5Qh69E" alt=""><figcaption><p>Refresh the Cluster Page</p></figcaption></figure>

4. If the problem persists, then perform the below step to make sure the kubeagent pod is in running state.

   ```
   kubectl wait --for=condition=ready pod -l app=kubeagent -n gopaddle-servers
   ```