Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Avatar for Username

Etsi tuesta

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.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

Firefox fails to connect using TLS to request for assets

  • 1 vastaus
  • 1 henkilöllä on sama ongelma
  • 3 näyttöä
  • Viimeisin kirjoittaja philipp

braiam
braiam
more options

When trying sites like monoprice, assets fail to load. For example https://images.monoprice.com/productmediumimages/149871.jpg works on curl and chromium but not in Firefox in any of my systems. Using safe mode and a clean profile doesn't help.

When trying sites like monoprice, assets fail to load. For example https://images.monoprice.com/productmediumimages/149871.jpg works on curl and chromium but not in Firefox in any of my systems. Using safe mode and a clean profile doesn't help.

Valittu ratkaisu

hi, thanks for reporting - it seams to be a problem with the configuration of some cdn nodes that twitter (and some other sites) are using to propagate their content. we're tracking this in https://bugzilla.mozilla.org/show_bug.cgi?id=1488240

a temporary workaround for this until a general fix is in place would be switching security.tls.version.max in about:config to 3. however you should revert that after a couple of days, as it might be detrimental to security in the long term.

Lue tämä vastaus kontekstissaan 👍 0

Kaikki vastaukset (1)

philipp
philipp
  • Moderator
more options

Valittu ratkaisu

hi, thanks for reporting - it seams to be a problem with the configuration of some cdn nodes that twitter (and some other sites) are using to propagate their content. we're tracking this in https://bugzilla.mozilla.org/show_bug.cgi?id=1488240

a temporary workaround for this until a general fix is in place would be switching security.tls.version.max in about:config to 3. however you should revert that after a couple of days, as it might be detrimental to security in the long term.