# Troubleshooting

<table><thead><tr><th width="298.512939453125">Error</th><th>Suggestion</th></tr></thead><tbody><tr><td><code>LabError: (code 1)</code>, i.e., could not connect to the API, <strong>with</strong> an <code>SSLError</code></td><td>See <a href="#connecting-from-a-corporate-network">connecting from a corporate network</a>.</td></tr><tr><td><code>UserError: (code 403) None</code><br><strong>without</strong> trace codes, i.e., =<code>None</code></td><td>Our firewall thinks you have bad intentions and is accidentally blocking your request. Please <a href="#reporting-errors">report the error</a> so we can help you.</td></tr><tr><td>Any other <code>LabError</code> or <code>UserError</code> <strong>with</strong> trace codes</td><td>See <a href="../remote-lab/error-handling-and-support">Error handling &#x26; support</a>.</td></tr><tr><td>Everything else</td><td>Reach us at <a href="mailto:support@causalchamber.ai">support@causalchamber.ai</a> or through any of the support channels provided during onboarding. We are happy to help :)</td></tr></tbody></table>

#### Reporting errors

{% hint style="info" %}
The best way to report an error is to send us the complete error trace, including the traceback and **trace codes**.
{% endhint %}

You can report an error through <support@causalchamber.ai> or any of the support channels provided during onboarding.

### Connecting from a corporate network

Firewalls in corporate networks often push their own root certificates for additional security. If you're connecting with your work computer from within a corporate network, e.g., office WiFi, you might see the following error:

{% code overflow="wrap" %}

```
LabError: (code 1) Could not connect to the API at https://api.causalchamber.ai/v0
...
Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate...
```

{% endcode %}

If this is the case, here's how to solve it

1. Visit <https://api.causalchamber.ai/health> with your **browser** to confirm the necessary certificates are installed on your computer. If they are, you should see a `scheduler_id`.
2. If that worked, you need to tell Python to use the right certificates. Run `pip install pip-system-certs`  in the Python environment from which you are calling our API.

That should fix it. If it doesn't or you're stuck, please [report the error](#reporting-errors) so we can help you :)