---
title: Charmhub | Deploy HTTPRequest Lego provider using Charmhub - The Open Operator
  Collection
description: Deploy the latest version of HTTPRequest Lego provider as a Kubernetes
  Operator on any cloud.
url: https://charmhub.io/httprequest-lego-provider/docs/troubleshoot-api-timeouts
---

# HTTPRequest Lego provider

[Canonical IS DevOps](https://charmhub.io/publisher/canonical-is-devops "View all packages from Canonical IS DevOps")

* [Canonical IS DevOps](https://charmhub.io/publisher/canonical-is-devops "View all packages from Canonical IS DevOps")

Platform:

stable 51

```
juju deploy httprequest-lego-provider
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

---

#### Relevant links

* [Homepage](https://charmhub.io/httprequest-lego-provider)

---

#### Contacts

* [Submit a bug](https://github.com/canonical/httprequest-lego-provider/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

# How to troubleshoot API timeouts

Some of the API calls will execute requests over the network from behind the scenes.

In the event you have a slow network connection this might result in timeouts manifesting as HTTP 500 errors for the API caller. This is more likely for larger Git repositories. If this is your case, adjusting the [`webserver-timeout`](https://charmhub.io/httprequest-lego-provider/configurations#webserver-timeout) configuration can help you solve this.

Note that if the HTTP Request LEGO provider is sitting behind a reverse proxy, the timeout might be occurring here. In the case of [Nginx ingress integrator](https://charmhub.io/nginx-ingress-integrator), you can change the [`proxy-read-timeout`](https://charmhub.io/nginx-ingress-integrator/configurations#proxy-read-timeout) configuration to adjust the timeout.

---