Mozilla 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

"Customer not provided" error leads to site lockout

  • 13 प्रत्युत्तर
  • 0 यह समस्या है
  • 1 view
  • के द्वारा अंतिम प्रतियुतर in4m8n

more options

I have a site where I have a valid login and password. I can login in Edge and FF Private Window, but in FF I get the attached message. Coninued tries gets me locked out for 24 hours.

I have whitelisted the site. Cleared caches and cookies, etc.

What does this mean and how can I fix it?

Thanks!

I have a site where I have a valid login and password. I can login in Edge and FF Private Window, but in FF I get the attached message. Coninued tries gets me locked out for 24 hours. I have whitelisted the site. Cleared caches and cookies, etc. What does this mean and how can I fix it? Thanks!
संलग्न स्क्रीनशॉट

All Replies (13)

more options

You can check for issues with Total Cookie Protection.

Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or if userChrome.css/userContent.css is causing the problem.

  • switch to the Default System theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window

Helpful?

more options

Thanks, but pretty generic answer to a pretty specific question. As I said, it works in private mode. The extensions still active, them the same, Chrome the same, etc. And it is a specific JSON error.

All of the above acknowledged. Of course, troubleshooting (as Private Window) will work. Total cookie protection on in BOTH standard and Private. Looking for something in between that causes it to complete in Private, but not standard.

Thanks.

Helpful?

more options

Also mentioned repeated attempts get me locked of of this account for 24 hours. SO any attempted solution shoul dbe targeted and stand a decent chance of success.

Helpful?

more options

So all your extensions are enabled in PB mode? Any messages in the Web Console that look relevant?

What response do you see in PB mode for this specific request?

Helpful?

more options

All extensions are. None I can find that are not.

In PB mode, it just works! I get logged in as expected after entering login and password. I have not looked at this either failing or succeeding in web console. Good idea.

I wish I knew how many attempsts over what period of time wor without a successful login or....it takes before being locked out so I can test more easily and know I will not get locked out.

The error is pretty specific and appears to be Oauth. But little I can find searching.

Helpful?

more options

OK, here comes TMI :) Hopefully this will help you help me....

I am logged in to another part of the domain in another tab. I go to new tab to login here and before I attempt I get this:

The script from “https://tmobilees.mpeasylink.com/mpel/mpel?href=https%3A%2F%2Fcommunity.t-mobile.com%2F&ref=&lang=en&country=&curr=undefined&region=” was loaded even though its MIME type (“”) is not a valid JavaScript MIME type. community.t-mobile.com

AppReady.allowLoadingElements() has not been called which might be an error. Make sure the app component calls it, that all route resolvers resolve, and there aren't any previous errors. rollbar.min.js:1:64172

After I try I get this:

Cookie “incap_ses_1341_2634229” has been rejected for invalid domain. initSession GET https://sso-us-west-2.api.insided.com/auth/oauth2/return?code=02.ettPpJZ97yYkA5D4H&state=ZIL1P9SoQm&session_num=0434ab17496625bd&userId=U-f01b0448-c2a7-4c72-9a12-5280adf3a0d9 [HTTP/2 400 Bad Request 84ms]

tradedesk TO BE BLOCKED FOR DONOTSELL utag.js:194:144 Loading failed for the <script> with source “https://cdn.appdynamics.com/adrum/adrum-latest.js”. v2:1:1 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://smetrics.t-mobile.com/b/ss/tmobusprod/10/JS-2.25.0/s92024250304563. (Reason: CORS request did not succeed). Status code: (null).

Content-Security-Policy: The page’s settings blocked the loading of a resource at https://sso-us-west-2.api.insided.com/favicon.ico (“default-src”). 2 FaviconLoader.jsm:180:19

See image:

Then I login SUCCESFULLY in a Private Window and the erros are so long I had to create a text file - attached. But it works there!!

Ahh, cannot upload a text file? Would you like to see all the contents?

I'll do it in the nextt post and you can delete tat post if you like.

~Bob

Helpful?

more options

This is from a SUCCESSFUL login in PB!! Too long for one post. More in next.

Some cookies are misusing the recommended “SameSite“ attribute 9 Cookie “visid_incap_2634229” has been rejected for invalid domain. authenticate Cookie “incap_ses_1341_2634229” has been rejected for invalid domain. authenticate Cookie “visid_incap_2634229” has been rejected for invalid domain. authenticate Cookie “incap_ses_1341_2634229” has been rejected for invalid domain. authenticate This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. community.t-mobile.com Some cookies are misusing the recommended “SameSite“ attribute 20 Google Analytics and Tag Manager is being shimmed by Firefox. See https://bugzilla.mozilla.org/show_bug.cgi?id=1713687 for details. sandbox eval code:1:9 cdl:: Debug is DISABLED rollbar.min.js:1:64172 Path :/ rollbar.min.js:1:64172

Helpful?

more options

Reading PageMap... Checking for :: GROUP_LIST rollbar.min.js:1:64172 Applicable tag length :: 9 rollbar.min.js:1:64172 Object { "cdl.page.siteName": "TMO", "cdl.page.channel": "Community", "cdl.page.subSection": "Home", "cdl.page.name": "Home Page", "cdl.envData.architecture": "NA" } rollbar.min.js:1:64172 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://js-agent.newrelic.com/nr-rum-1.260.1.min.js. (Reason: CORS request did not succeed). Status code: (null). The resource at “<URL>” was blocked because content blocking is enabled. 2 None of the “sha512” hashes in the integrity attribute match the content of the subresource. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. community.t-mobile.com New Relic: A problem occurred when starting up session manager. This page will not start or extend any session. rollbar.min.js:1:64172 ChunkLoadError: Loading chunk 75 failed. (error: https://js-agent.newrelic.com/nr-rum-1.260.1.min.js)

   j https://community.t-mobile.com/:79
   e https://community.t-mobile.com/:79
   e https://community.t-mobile.com/:79
   R https://community.t-mobile.com/:79
   api https://community.t-mobile.com/:79
   s https://community.t-mobile.com/:79
   o https://community.t-mobile.com/:79
   api https://community.t-mobile.com/:79
   E https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79

rollbar.min.js:1:64172 New Relic: A problem occurred when starting up session manager. This page will not start or extend any session. rollbar.min.js:1:64172 ChunkLoadError: Loading chunk 75 failed. (error: https://js-agent.newrelic.com/nr-rum-1.260.1.min.js)

   j https://community.t-mobile.com/:79
   e https://community.t-mobile.com/:79
   e https://community.t-mobile.com/:79
   R https://community.t-mobile.com/:79
   api https://community.t-mobile.com/:79
   s https://community.t-mobile.com/:79
   o https://community.t-mobile.com/:79
   api https://community.t-mobile.com/:79
   E https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79

rollbar.min.js:1:64172 New Relic: A problem occurred when starting up session manager. This page will not start or extend any session. rollbar.min.js:1:64172 ChunkLoadError: Loading chunk 75 failed. (error: https://js-agent.newrelic.com/nr-rum-1.260.1.min.js)

   j https://community.t-mobile.com/:79
   e https://community.t-mobile.com/:79
   e https://community.t-mobile.com/:79
   R https://community.t-mobile.com/:79
   api https://community.t-mobile.com/:79
   s https://community.t-mobile.com/:79
   o https://community.t-mobile.com/:79
   api https://community.t-mobile.com/:79
   E https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79

rollbar.min.js:1:64172 New Relic: Downloading runtime APIs failed... rollbar.min.js:1:64172 ChunkLoadError: Loading chunk 75 failed. (error: https://js-agent.newrelic.com/nr-rum-1.260.1.min.js)

   j https://community.t-mobile.com/:79
   e https://community.t-mobile.com/:79
   e https://community.t-mobile.com/:79
   R https://community.t-mobile.com/:79
   api https://community.t-mobile.com/:79
   s https://community.t-mobile.com/:79
   o https://community.t-mobile.com/:79
   api https://community.t-mobile.com/:79
   E https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79
   <anonymous> https://community.t-mobile.com/:79

rollbar.min.js:1:64172 jQuery.Deferred exception: MutationObserver.observe: Argument 1 is not an object. @https://community.t-mobile.com/:569:23 l@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:30108 19755/</Deferred/then/a/</c<@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:30410 setTimeout handler*19755/</Deferred/then/a/<@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:30619 u@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:28390 fireWith@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:29138 fire@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:29174 u@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:28390 fireWith@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:29138 ready@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:32124 z@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:31902 EventListener.handleEvent*19755/<@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:32273 19755/<@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:194 19755@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2:307 __webpack_require__@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1:131048 93959@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1:69970 __webpack_require__@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1:131048 37815@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1:75052 __webpack_require__@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1:131048 __webpack_exports__<@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1:135144 __webpack_require__.O@https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1:131466 @https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1:135194 @https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1:135218 <pre>undefined rollbar.min.js:1:64172

Uncaught TypeError: MutationObserver.observe: Argument 1 is not an object.

   <anonymous> https://community.t-mobile.com/:569
   l https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   c https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   setTimeout handler*19755/</Deferred/then/a/< https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   u https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   fireWith https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   fire https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   u https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   fireWith https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   ready https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   z https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   19755 https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   19755 https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   19755 https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/755.js:2
   __webpack_require__ https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1
   93959 https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1
   __webpack_require__ https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1
   37815 https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1
   __webpack_require__ https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1
   __webpack_exports__ https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1
   O https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1
   <anonymous> https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1
   <anonymous> https://dowpznhhyvkm4.cloudfront.net/2024-06-10-12-51-41-e3f253f494/dist/js/app.js:1
</pre>

community.t-mobile.com:569:23 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://js-agent.newrelic.com/nr-rum-1.260.1.min.js. (Reason: CORS request did not succeed). Status code: (null

Helpful?

more options

You can remove all data stored in Firefox for a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History -> Show All History" or "View -> Sidebar -> History").

Using "Forget About This Site" will remove all data stored in Firefox for this domain like history and cookies and passwords and exceptions and cache, so be careful. If you have a password or other data for that domain that you do not want to lose, make sure to backup this data or make a note.

You can't recover from this 'forget' unless you have a backup of involved files.

If you revisit a 'forgotten' website, data for that website will be saved once again.

Helpful?

more options

And you think that fixes this issue? Or just a temporary bandaid. And then why does it work in PB?

Helpful?

more options

A major difference between a regular window and a private window is that PB windows keep all data in memory and do not use the disk cache, but use a separate cookie jar kept in memory, cookies from regular windows stored in cookies.sqlite in the profile folder can't be accessed. All PB mode windows share the same PB mode cookies jar, you need to close all PB windows or close and restart Firefox to start with a fresh PB cookies jar.

Helpful?

more options

Well, feels like that explains why PB works. But then how to I get a consistent access to that page in normal FF? I have not been able to do that even once and I use the logins, cookies, etc in many other T-mobile sites.

Helpful?

more options

OK, found a setting in my cookie blocker that allows this to work as expected now. Thanks for the help folks.

Helpful?

प्रश्न पूछें

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.