Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Search Support

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.

Learn More

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

Firefox fails to connect using TLS to request for assets

  • 1 amsa
  • 1 yana da wannan matsala
  • 14 views
  • Amsa ta ƙarshe daga 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.

Mafitar da aka zaɓa

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.

Karanta wannan amsa a matsayinta 👍 0

All Replies (1)

philipp
philipp
  • Moderator
more options

Zaɓi Mafita

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.