Avatar for Username

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

אשכול זה הועבר לארכיון. נא לשאול שאלה חדשה אם יש לך צורך בעזרה.

how to resolve a 502 bad gateway error on https://fhr.cdn.mozilla.net/en-US/v4/

  • 2 תגובות
  • 14 have this problem
  • 56 views
  • תגובה אחרונה מאת philipp

goldbit
goldbit
more options

After upgrading to new 44 today, i now get 502 bad gateway errors on https://fhr.cdn.mozilla.net/en-US/v4/.

here is some additional information:

request headers: Host: fhr.cdn.mozilla.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br DNT: 1 Connection: keep-alive Cache-Control: max-age=0

response headers: Age: 33 Connection: keep-alive Content-Length: 587 Content-Type: text/html Date: Wed, 27 Jan 2016 12:32:49 GMT Server: CloudFront X-Amz-Cf-Id: QkFi40evQdvNL2pGIId1kPGNWkrWrHXFsTu5QsV5dNL9WNyh6gm7pw== X-Cache: Error from cloudfront via: 1.1 26323e33c40f7d3c5faf3b27606bb0b1.cloudfront.net (CloudFront)

After upgrading to new 44 today, i now get 502 bad gateway errors on https://fhr.cdn.mozilla.net/en-US/v4/. here is some additional information: request headers: Host: fhr.cdn.mozilla.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br DNT: 1 Connection: keep-alive Cache-Control: max-age=0 response headers: Age: 33 Connection: keep-alive Content-Length: 587 Content-Type: text/html Date: Wed, 27 Jan 2016 12:32:49 GMT Server: CloudFront X-Amz-Cf-Id: QkFi40evQdvNL2pGIId1kPGNWkrWrHXFsTu5QsV5dNL9WNyh6gm7pw== X-Cache: Error from cloudfront via: 1.1 26323e33c40f7d3c5faf3b27606bb0b1.cloudfront.net (CloudFront)

פתרון נבחר

hi goldbit, thanks for reporting this - it is currently a server-side issue with the health-report infrastructure unfortunately (and not related to a particular firefox version). mozilla's webops are looking into the matter already...

Read this answer in context 👍 2

כל התגובות (2)

philipp
philipp
  • Moderator
more options

פתרון נבחר

hi goldbit, thanks for reporting this - it is currently a server-side issue with the health-report infrastructure unfortunately (and not related to a particular firefox version). mozilla's webops are looking into the matter already...

philipp
philipp
  • Moderator
more options

i've just heard back that there is a temporary fix in place now.