Hi RandomTroll, where does body.Illustrated.netTimeout.neterror appear? Is that in the Web Console (Console tab of the developer tools)? It doesn't sound like a built-in reference, so it may be a message from one of the scripts in the page.

I notice the Firefox you posted with has a number of content blockers installed; a timeout could be caused by one of those or by an entry in a hosts file. But on the public PC, presumably it's not customized to block anything, so that could indicate the site doesn't work well in Firefox.

Same thing happens in safe mode.

RandomTroll said

Same thing happens in safe mode.

Can you also rule out Firefox's Content Blocking feature as a possible source of interference? It displays a shield icon toward the left end of the address bar, near the lock icon when there is either blocked or blockable content in a page. More info on managing the Tracking Protection feature in this article: Content Blocking.

Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)?

No. This is the only page on which it happens. And it's irrelevant: the page won't even come up; my problem isn't what happens when I try to log in: I can't get the page.

I assume it's t-mobile's fault but they haven't helped me - I've been on them since April. I ran it in web developer to see what that showed me. I hoped a Firefox-savvy person would know which timeout is associated with that error.

BTW the 'Network' aspect of web developer reports

domcontentloaded: 2:18

I hoped 138 seconds would match one of the timeouts, but it doesn't.

Can you test the domain in about:networking DNS lookup or check the Network Monitor ?

• https://developer.mozilla.org/en-US/Tools/Network_Monitor

jscher2000 said

where does body.Illustrated.netTimeout.neterror appear? Is that in the Web Console (Console tab of the developer tools)?

Yes.

jscher2000 said

Can you also rule out Firefox's Content Blocking feature as a possible source of interference? It displays a shield icon toward the left end of the address bar, near the lock icon when there is either blocked or blockable content in a page.

I don't seem to have that anymore. I just noticed its absence.

cor-el said

Can you test the domain in about:networking DNS lookup or check the Network Monitor ?

Domain: IPs 10.189.136.20 2607:fb90:c13e:fffd::30

and

One request 0 B / 0 B transferred Finish: 301 ms DOMContentLoaded: 369 ms

FWIW, a traceroute doesn't get through either; either name resolution or the route is bad. All addresses are in t-mobile's intranet - cause I'm a t-mobile customer.

debug reports:

2019-09-23 14:27:58.830171 UTC - [Parent 29782: Socket Thread]: D/nsHostResolver Resolving host [mim.t-mobile.com] - bypassing cache type 0. [this=0x7f5c2d04a2e0]

2019-09-23 14:27:58.830200 UTC - [Parent 29782: Socket Thread]: D/nsHostResolver   No usable record in cache for host [mim.t-mobile.com] type 0.

2019-09-23 14:27:58.830228 UTC - [Parent 29782: Socket Thread]: D/nsHostResolver   DNS lookup for host [mim.t-mobile.com] blocking pending 'getaddrinfo' or trr query: callback [0x7f5c13429280]

2019-09-23 14:27:58.830248 UTC - [Parent 29782: DNS Resolver #56]: E/nsHostResolver DNS lookup thread - Calling getaddrinfo for host [mim.t-mobile.com].

2019-09-23 14:27:58.834805 UTC - [Parent 29782: DNS Resolver #56]: E/nsHostResolver DNS lookup thread - lookup completed for host [mim.t-mobile.com]: success.

2019-09-23 14:27:58.834849 UTC - [Parent 29782: DNS Resolver #56]: D/nsHostResolver nsHostResolver::CompleteLookup mim.t-mobile.com 0x7f5c127b6380 0 trr=0 stillResolving=0

2019-09-23 14:27:58.834871 UTC - [Parent 29782: DNS Resolver #56]: D/nsHostResolver Caching host [mim.t-mobile.com] record for 60 seconds (grace 60).

2019-09-23 14:27:58.834880 UTC - [Parent 29782: DNS Resolver #56]: D/nsHostResolver CompleteLookup: mim.t-mobile.com has 10.175.136.20

2019-09-23 14:27:58.835352 UTC - [Parent 29782: Socket Thread]: D/nsHostResolver Checking blacklist for host [mim.t-mobile.com], host record [0x7f5c13dce820].

2019-09-23 14:28:05.926940 UTC - [Parent 29782: Socket Thread]: D/nsHostResolver Adding address to blacklist for host [mim.t-mobile.com], host record [0x7f5c14765040].used trr=0

2019-09-23 14:28:05.926951 UTC - [Parent 29782: Socket Thread]: D/nsHostResolver Successfully adding address [10.175.136.20] to blacklist for host [mim.t-mobile.com].

2019-09-23 14:28:05.926965 UTC - [Parent 29782: Socket Thread]: D/nsHostResolver Checking blacklist for host [mim.t-mobile.com], host record [0x7f5c14765040].