Closed Bug 1364636 Opened 8 years ago Closed 8 years ago

esfrontline.bugzilla.mozilla.org returning 400s

Categories

(bugzilla.mozilla.org :: Infrastructure, enhancement)

Product:
bugzilla.mozilla.org
Component:
Infrastructure
Version:
Production
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: emceeaich, Unassigned)

References

(
URL
)

Details

When requesting stats from ekyle's Elasticsearch dashboard (see urls), we get 400's trying to connect to the ES host
This is not an urgent thing for this (May 13/14) weekend, but checking into Monday would be good.
The app that proxies requests to the ES cluster does provide much in the way of logging, but there are a large number of 'Not allowed' warnings that look like someone was scanning/probing the site looking for common vulnerabilities, which my have led to the app/cluster throwing 400s. I don't see any 400s currently with the URL provided, but the dashboard doesn't appear to display anything useful either. Kyle, any thoughts?
Flags: needinfo?(klahnakoski)
I have verified that the private cluster is working: https://people-mozilla.org/~klahnakoski/modevmetrics/Tutorial04-Private.html Ensure you are on the MozillaVPN and you have disabled mixed content blocking (the private cluster only has http (no https) access)
Flags: needinfo?(klahnakoski)
I'm not comfortable disabling mixed content blocking to use this, can someone please check the public cluster and restart it if necessary?
Please do not reboot, every reboot runs a risk of loosing the indexes, requiring a rebuild. The private cluster is working. Problem is web "standards" have changed so fast that in the past 5 years public static websites have moved to https and http data services are now blocked by browsers. Mixed content blocking is to prevent https websites from accessing http services. Be sure your html/javascript is only served from an not-encrypted location, or standup a https proxy that will relay queries to the private cluster, or disable mixed content blocking. Those are the only solutions for now.
oh dear, I was talking about the private cluster not the public cluster...
The public cluster is working. Unfortunately, Firefox has a bug where if it gets just one response (400 or not) without an `access-control-allow-origin` header, it will never send AJAX requests to that URL again. Firefox must be rebooted before more requests can be made. If you can figure out which response was missing the `access-control-allow-origin` header, we can fix it, like in this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1254742
I'm able to access public cluster through Chrome so closing this for now.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.