> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/troubleshooting/cloud-cost-management/autostopping-troubleshooting.md).

# Troubleshoot AutoStopping rule and proxy

Access rule logs to troubleshoot AutoStopping rule and proxy issues.

### Access AutoStopping rule logs <a href="#access-autostopping-rule-logs" id="access-autostopping-rule-logs"></a>

To access rule logs, complete the following steps:

1. In the Harness application, navigate to **Cloud Costs**.
2. Select **AutoStopping Rules**.
3. Select the rule that you want to troubleshoot.

You can view the logs on the **Summary** tab.

The AutoStopping rule logs include entries for the following issues:

* Permission errors
* Fixed-schedule discrepancies
* Virtual machine (VM) start and stop errors
* Kubernetes (K8s) workload scaling issues
* Traffic detection errors
* Configuration errors

Review the logs to identify and address the issue.

### AutoStopping Proxy logs <a href="#autostopping-proxy-logs" id="autostopping-proxy-logs"></a>

The AutoStopping proxy contains these three services:

1. Envoy
2. LW Proxy
3. TCP Proxy

The AutoStopping proxy logs show network and application programming interface (API) issues. They include unreachable networks, closed security groups, and invalid or expired API tokens.

Access the VM through Secure Shell (SSH) to get logs for each service. Run the command for the service:

#### Envoy

```bash
journalctl -u envoy
```

#### LW Proxy

```bash
journalctl -u lw_proxy
```

#### TCP Proxy

```bash
journalctl -u lw_tcp_proxy
```