This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

This thread was archived. Please ask a new question if you need help.

Firefox fails to connect using TLS to request for assets

  • 1 reply
  • 1 has this problem
  • 3 views
  • Last reply by 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.

Chosen solution

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.

Read this answer in context 👍 0

All Replies (1)

philipp
philipp
  • Moderator
more options

Chosen Solution

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.