Hello,

First, please note that you are using Firefox 115, while the latest version is 139. Some sites may stop supporting old browsers' versions.

Second, could you please list the sites you are experiencing issues with? We may try to help with at least some of them.

Denys,

Thank you for responding but where are you getting Ver 115 for Firefox from????

According to the information on my Firefox Help screen, I do have Ver 139 installed. See enclosed pic.

Presuming the Ver 139 is installed, then that seem to still be a problem.

Various website but the last one was www.usaa.com and https://www.usaa.com/my/logon?logoffjump=true&wa_ref=pub_global_log_on

The error msg I get is:

We are unable to complete your request. Our system is currently unavailable. Please try again later.

jsaint285,

Sorry for misleading you about your browser version.

The website you mentioned loads just fine in my Firefox (of the same version). Could you please specify, is the error you get Firefox-origin or site-origin? I mean, can you see any elements of the site's interface? The screenshot is also appreciated.

Denys,

As requested enclosed is a screen shot of the usaa.com login website and the indicated error message.

NOTE: I can go to Chrome and log in without any problems. The issue is FIREFOX related exclusively.

What you see in the webpage background is all that I see. I do not have any access to "elements" of the webpage as I do not control it.

In your screenshot, it looks like you never get the second part of the form where you enter your password.

As a test, could you disable Tracking Protection on the page? Here's how: click the "shield" icon at the left end of the address bar (to the left of the lock icon). On the panel that drops, click the blue slider switch to turn off protection. The page should reload, but use Ctrl+Shift+R to force a reload that bypasses old cached files. Then try the form again. Any improvement?

Jscher2000

I did what you asked but got the same results. See enclosed screen shot # 2

Further, from my perspective this is not a solution, as I used to be able to access the USAA.com website without any problems, or any other website for that matter all without all the BS crap I seemed to be going through today.

I have not changed any settings in FIREFOX, nor have I installed anything recently in the way of new software.

So what is causing this to happen?

Thanks.

I don't know why you are getting that message. To investigate further:

(1) Could you open the "Web Console" in the bottom part of the tab by pressing Ctrl+Shift+K. Serious messages usually are in red text on a pink background. Can you see anything that mentions requests being blocked?

(Example screenshot attached from my session, with just a cookie error.)

(2) Could you switch to the "Network" panel and reload the page using Ctrl+Shift+R. Then click the little trash can above the list of URLs to clear the list. Then enter your user name and click Next. Does the Network Monitor show the calls to "authenticate" and, if so, what kind of status codes do you get back?

(Example screenshot attached showing a "200" code, which indicates Success, for everything.)

As a separate question, why does your Online ID show as a row of asterisks and mine shows as plain text? That difference is a little odd.

jscher2000

As to the first part above, the following warning messages are displayed:

Content-Security-Policy: This site (https://www.usaa.com) has a Report-Only policy without a report-uri directive nor a report-to directive. CSP will not block and cannot report violations of this policy. logon Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. logon:9:19 unreachable code after return statement NwIB:1:203674 unreachable code after return statement NwIB:1:340698 Use of the orientation sensor is deprecated. NwIB:1:96006 Use of the motion sensor is deprecated. NwIB:1:96121 InstallTrigger is deprecated and will be removed in the future. NwIB:1:100940 asm.js type error: cannot create array view without an asm.js heap parameter utag.318.js:8:120330 WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. NwIB:1:261732 WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. utag.516.js:6340:220 Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and Enhanced Tracking Protection is enabled. 3 WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER.

As to the second part, under the authenticate link is the following, plus I am providing a screen shot of the network list:

ms/</window.XMLHttpRequest.prototype.send https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:518922 91579/e.exports/< https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:385178 91579/e.exports https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:383345 75025/e.exports https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:326589 36200/l.prototype.request https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:126348 36200/</l.prototype[e] https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:126801 64695/e.exports/< https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:282681 yu/< https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:536195 47706/r/</</< https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:181650 mainRouting https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:613037 _d</memberSubmitHandler/</< https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:612981 _d</memberSubmitHandler/< https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:612989 47706/r/</</< https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:181650 memberSubmitHandler https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:612806 submitAfterCallbackCompletion https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:609621 onSubmit https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:609223 Mp https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:587251 Fp https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:587917 od/od/u/t.submit/f< https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:595578 Pp/< https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:585067 vi https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:235:330 ui https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:65:27 xi https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:65:81 zg https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:88:405 rg https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:89:319 hg/< https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:99:170 <anonymous> https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:273:292 ti https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:63:406 hg https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:92:150 be https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:79:16 he https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:78:112 unstable_runWithPriority https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:24:26 Za https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:106:8 <anonymous> https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:273:157 Ki https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:77:407 (Async: EventListener.handleEvent) Bg https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:91:160 Fg https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:90:308 Cg/< https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:90:1 Cg https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:89:479 tf https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:223:86 ak https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:224:163 zd https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:224:387 M.render https://www.usaa.com/utils/externals/react!react-dom/17.0.2/react!react-dom.min.js:276:314 <anonymous> https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:735869 <anonymous> https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:736102 <anonymous> https://www.usaa.com/my/logon/ent-unified-logon-web.b45fbdfda87ed77f41d1.js:3:736106 </p>

Not sure what all of that means, but hopefully you do.

Best wishes and thanks.

/s/ James

Oh as to the ****** for the login. I did not want my login name to be displayed so I replaced it with ***** for security reasons

Thank you for checking that. On the Console side, it's a little hard to read. These two might be errors (red/pink):

• unreachable code after return statement (in) NwIB:1:203674
• unreachable code after return statement (in) NwIB:1:340698

The others sound like warnings that I also am seeing but which don't seem to affect how the site runs in my Firefox.

On the Network Monitor list, the response for authenticate is much different: you're getting back 4.44 kb of HTML, while I'm getting 1613 kb of JSON data. So something is going wrong with that request, but I don't know whether the issue is that your Firefox is omitting/modifying something the server requires, or there is some other reason the server doesn't want to return the normal response.

Have you changed any privacy settings or add-ons recently?

jscher2000,

I have no idea what any of your message means or how it relates to me.

As previously indicated no I have not made any changes in either privacy settings or add-ons.

although come to think of it ... I did try to add two different Firefox add-ons that were recommended by Mozilla to eliminate the damn Google login pop-up when I first open the browser to my google.com home page.

One of them was Google Sign-in Popup Blocker by Xavier that was recommended by Paul of Mozilla. I can't remember what the other one was ... I think it was ... Block Sign In With Google by zaporter

Neither one of them worked, so I deleted them.

Other than that I have not added anything software wise.

You could try a clean profile. This takes about 3 minutes, plus the time to test your problem site(s).

(1) Inside Firefox, type or paste about:profiles in the address bar and press Enter/Return to load it.

(2) Take a quick glance at the page and make a mental note of which Profile has this notation: This is the profile in use and it cannot be deleted. That is your current default profile.

(3) Click the "Create a New Profile" button, then click Next. Assign a name like Test2025, ignore the option to relocate the profile folder, and click the Finish button.

(4) Firefox will switch your default profile to the new one, so click the Set as Default Profile button for your regular one to avoid an unwanted surprise at your next startup.

(5) Scroll down to Test2025 and click its Launch profile in new browser button.

Firefox should open a new window that looks like a brand new, uncustomized installation. (Your existing Firefox window(s) should not be affected.) Please ignore any tabs enticing you to connect to a Sync account or to activate extensions found on your system to get a clean test.

(6) Try USAA in the new profile. Any difference?

When you are done with the experiment, you can close the extra window without affecting your regular Firefox profile. (Test2025 will remain available for future testing.)

jscher2000,

I will give that a try, but before I do so, enclosed is a screen shot of the existing configurations. Do you see any problems with have all of these in place, or should I delete two of them?

Okay I did what you asked and the Test2025 profile was able to access the usaa.com website and get login without any problems.

That being said, what needs to be changed to the existing profile or profiles to be able to keep my current setup but that will allow me to get access to the current websites that are being blocked.

Note: This is a lot of technical stuff I am not readily familiar with, or what I might like to be familiar with.

Thank you.

/s/ James

jscher2000,

interesting effect. The Profile: default-release appears to be the only one having a problem with accessing websites, i.e. usaa.com

The Profile: default can access the usaa.com website with no problem; Same Same for the Profile: default-release-1.

However, neither of those profile has the set up like the Profile: default-release has.

So I guess my question would be how to transfer the set up of the Profile: default-release into one or both of the other profiles, and then delete the current Profile: default-release in favor of one of the other ones?

Best wishes,

/s/ James

And of course in the copying process, how to eliminate the current problem that is not allowing access to websites?

Okay, I think I was able to figure out how to reconfig the Profile: default-release-1 to look like the Profile: default-release that includes my menu bar, bookmarks and theme layout.

Would I be correct in that based on what you have suggested above, and the associated results the next step should be to remove the Profile: default-release and make the Profile: default-release-1 the actual default profile.

Or is the anything else you would recommend to do prior to me doing this?

Hi, please don't delete anything. Inevitably, people forget little details and you can open the old profile on the side to find, for example, some missing Firefox or add-on settings or older history. At this point, you can simply change your default profile.

One possibility to try to research the problem, if it's a setting, is to use a file comparison tool to compare the prefs.js file in the two profile folders. These files contain a lot of irrelevant lines, such as a timestamp for the last update check, but they also could reveal customized privacy settings, or other relevant settings, in your regular profile that are not in the newer/cleaner profile.

I use WinMerge (https://winmerge.org/) for these kinds of comparisons, but you could even use Microsoft Word's legal blackline feature.

Hello again,

You have done a really impressive job here, so I fell a bit embarrassed to ask... But did you try clearing cookies and data for that site? Saved data is the most obvious possible difference between your old and fresh profiles. If you did, sorry for interrupting.

1st to Denys, Yes I did previously clear the cookies and cache, and I also restarted my computer many times. None of that simplistic suggestion worked.

2nd to jscher2000,

I did the comparison of the two prefs.js files as suggested, but your system is not allowing me to upload the two PDF files.

My software program did not produce anything in its comparison that I could understand, so I did a line item by line item comparison, color coding the differences: Red for the original default profile file that was causing problems and blue for the replacement profile file that seems to be working very well. If the indicated section was the same, the colors stayed with the default black font. I did not pay any attention to the numbers associated with each item, as I did not understand them or figured they were time / date stamps of so kind of other.

There were certain sections that while the "title" of the section was the same in both, the content contained in that section was not. Those sections I highlighted in the same different color from the red and blue highlights.

For example bottom of page 6/top of page 7; again bottom of page 9/top of page 10; and finally the middle of page 11.

I just tried to upload the two PDF files, but your Mozilla system seems to only want image files.

Give both files run 23 pages that is not possible to create image files of them to be of any use.

How can I get these to you so you can review them?

Many thanks for your assistance.

/s/ James T Saint, CCIM COO