Avatar for Username

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

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

  • 2 件の返信
  • 14 人がこの問題に困っています
  • 56 回表示
  • 最後の返信者: 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...

この回答をすべて読む 👍 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.