We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Firefox fails to connect using TLS to request for assets

  • 1 antwoord
  • 1 het hierdie probleem
  • 14 views
  • Laaste antwoord deur 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.

Gekose oplossing

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.

Lees dié antwoord in konteks 👍 0

All Replies (1)

philipp
philipp
  • Moderator
more options

Gekose oplossing

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.