Matthew Horan

> Have you ever succeeded with this client before? If yes, can you help try to reset the settings through the tray icon -> Reset Settings and start over to...

As of this morning a few of us have updated our client and it seems to be working again! No more "unknown error".

I had considered submitting a patch but didn't feel comfortable contributing on my own. Now I definitely don't feel comfortable contributing. Perhaps someone else will see this and submit a...

I apologize that you interpreted my response as being unkind; that is also how I interpreted your response. I respect your time and understand that this issue is not a...

I just checked my logs, but I think any error from the time of this issue must have rotated through by now. acme-client ultimately runs via cron, but the FreeBSD...

I've been experiencing this with some regularity in one of my projects. The query is not very demanding and generally returns rather quickly. However, my Grafana alert rules periodically error...

I set up the frontend outside of the GKE cluster to rule that out as a factor. I'm not getting timeouts from the GCM request anymore, but I did get...

After digging through my ingress logs it would seem that these requests are indeed being canceled by Grafana due to a timeout. Despite setting my query timeout to 2m, the...

I would see timeouts in the Grafana UI for various graphs as well until I added the following to my Ingress: ``` metadata: annotations: nginx.ingress.kubernetes.io/proxy-next-upstream: error timeout http_503 nginx.ingress.kubernetes.io/proxy-connect-timeout: "3"...

:wave: hey Lee! I sent my project details over to you via email. I am fairly certain the frontend is not to blame here as well. I tried running the...