You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting approximately Nov 26th, we've been getting intermittent alerts from Updown that ZAP Search is down. The validity of these reports was backed up on 12/3 by Sarah Whitham sharing that Sara Avila was getting a 502 Bad Gateway error when trying to visit ZAP Search.
Cross reference outage times with logs in Heroku to identify root cause
Document research and share suggested next steps.
The text was updated successfully, but these errors were encountered:
@TangoYankee@TylerMatteo
I thought I was onto something with the alert noticing the description Client Request Interrupted below but it seems to be a red herring.
I searched the logs for more Client Request Interrupted incidents and they don't match up with any of the alerts in Uptown.
I checked the error logs in the reverse proxy. It seems there are several requests a minute that are unable to connect to IPv6 addresses at port 443. Multiple applications have their own connection failures- zola, applicant portal, community profiles, etc. Maybe there is a misconfiguration in Netlify? Either in the IPv6 addresses or their SSL certificates
Starting approximately Nov 26th, we've been getting intermittent alerts from Updown that ZAP Search is down. The validity of these reports was backed up on 12/3 by Sarah Whitham sharing that Sara Avila was getting a 502 Bad Gateway error when trying to visit ZAP Search.
The text was updated successfully, but these errors were encountered: