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 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, you can change the proxy-read-timeout configuration to adjust the timeout.