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!

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.

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

ssl_error_rx_record_too_long keep getting this error message when trying to access amazon secure pages also on IE and on firefox android what is it?

  • 2 پاسخ
  • 45 have this problem
  • 2 views
  • آخرین پاسخ توسّط chet10

more options

I did reset firefox but nothing changed + run malware adware and antivirus ; as said above it also happens with IE on my desktop and on firefox android with my tablet (sync with desktop)

I did reset firefox but nothing changed + run malware adware and antivirus ; as said above it also happens with IE on my desktop and on firefox android with my tablet (sync with desktop)

Chosen solution

You can try to reset (power off/on) the router.

Are you using a proxy or a direct connection?

Check the connection settings.

If you do not need to use a proxy to connect to internet then try to select "No Proxy" if "Use the system proxy settings" or one of the others do not work properly.

See "Firefox connection settings":

Read this answer in context 👍 3

All Replies (2)

more options

Chosen Solution

You can try to reset (power off/on) the router.

Are you using a proxy or a direct connection?

Check the connection settings.

If you do not need to use a proxy to connect to internet then try to select "No Proxy" if "Use the system proxy settings" or one of the others do not work properly.

See "Firefox connection settings":

more options

Many thanks cor-el, I discovered that since I connect direct choosing the no proxy option has solved the problem; Hoping I am not speaking too soon... Cheers