X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Failing to signon to Macy's web site & receive 'A technical error has occurred. For assistance, please call' missive.

Kuphostiwe

When I attempt to sign in to Macy's web site using Firefox (https://www.macys.com/account/signin?lid=sign_in&cm_sp=macys_account-_-macys_credit_card-_-sign_in). I receive the following message: 'A technical error has occurred. For assistance, please call 1-800-289-6229'. When I called their service department with this problem, they advised me to use Chrome, which signed in to the same site without a problem. So far I only use Chrome for Macy's bill payment. I enjoy using Firefox. Thank you ahead of time for any and all support! Cornyst

When I attempt to sign in to Macy's web site using Firefox (https://www.macys.com/account/signin?lid=sign_in&cm_sp=macys_account-_-macys_credit_card-_-sign_in). I receive the following message: 'A technical error has occurred. For assistance, please call 1-800-289-6229'. When I called their service department with this problem, they advised me to use Chrome, which signed in to the same site without a problem. So far I only use Chrome for Macy's bill payment. I enjoy using Firefox. Thank you ahead of time for any and all support! Cornyst
Isicaphuno

Eminye Imininingwane Yohlelo

Fakela amapulagi

OpenH264 Video Codec provided by Cisco Systems 1.7.1 Widevine content decryption module provided by google 1.4.9.1088

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Eminye Imininingwane

jscher2000
  • Top 10 Contributor
8514 izisombululo 69541 izimpendulo
Kuphostiwe

They didn't give you much to go on, did they?

Websites use a series of test to try to prevent automated access, so possibly something about the way your Firefox responded was considered suspicious. Possibly some blocked content, blocked cookies, blocked storage, or modified headers is a factor. If you've done any customization to make Firefox load less crap or share less data, it's possible that is the problem, but unless someone wants to test the site with lots of different settings, I don't know that we'd come up with a definitive diagnosis.

For future reference, you might look at cookie settings and Content Blocking as the most obvious potential culprits. If it's a site you have visited in Firefox in the past, clearing the cache can also help to avoid a mismatch of old and new files. Some articles:

They didn't give you much to go on, did they? Websites use a series of test to try to prevent automated access, so possibly something about the way your Firefox responded was considered suspicious. Possibly some blocked content, blocked cookies, blocked storage, or modified headers is a factor. If you've done any customization to make Firefox load less crap or share less data, it's possible that is the problem, but unless someone wants to test the site with lots of different settings, I don't know that we'd come up with a definitive diagnosis. For future reference, you might look at cookie settings and Content Blocking as the most obvious potential culprits. If it's a site you have visited in Firefox in the past, clearing the cache can also help to avoid a mismatch of old and new files. Some articles: * [[Websites say cookies are blocked - Unblock them]] * [[Content blocking]] * [[How to clear the Firefox cache]]
Ingabe lokhu kube usizo kuwena? 0
Isicaphuno
cor-el
  • Top 10 Contributor
  • Moderator
17276 izisombululo 156150 izimpendulo
Kuphostiwe

What Firefox version do you use?

Are you possibly using "Resist Fingerprinting"?

You can check this pref on the about:config page to see if resist fingerprinting (RFP) is enabled and if this pref is user set (bold) reset to false via the right-click context menu.

  • privacy.resistFingerprinting = false

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

What Firefox version do you use? Are you possibly using "Resist Fingerprinting"? *https://support.mozilla.org/en-US/kb/firefox-protection-against-fingerprinting You can check this pref on the <b>about:config</b> page to see if resist fingerprinting (RFP) is enabled and if this pref is user set (bold) reset to false via the right-click context menu. *privacy.resistFingerprinting = false You can open the <b>about:config</b> page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue. *https://support.mozilla.org/en-US/kb/about-config-editor-firefox
Ingabe lokhu kube usizo kuwena? 0
Isicaphuno

Umnikazi wombuzo

Thank you for your quick response. I followed all instructions for Cookies, Content and Cache. still no joy! I don't believe that it is a Firefox issue at all.

FYI, I was able to sign in, successfully, via Windows 10 Mobile Microsoft Edge.

Again thank you for quick respose and suggestions. Cornyst

Thank you for your quick response. I followed all instructions for Cookies, Content and Cache. still no joy! I don't believe that it is a Firefox issue at all. FYI, I was able to sign in, successfully, via Windows 10 Mobile Microsoft Edge. Again thank you for quick respose and suggestions. Cornyst
Ingabe lokhu kube usizo kuwena?
Isicaphuno
Buza umbuzo

Kufanele ulogele ukungena ku-akhawunti yakho ukuze uphendule amaphosti. Uyacelwauqale umbuzo omusha, uma ungekabi nayo i-akhawunti namanje.