All other Mozilla sites I've used work fine. So did treeherder until a day or two ago. It starts to load for a few seconds, then displays an error page: """ The connection was interrupted The connection to treeherder.mozilla.org was interrupted while the page was loading. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer's network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web. """ No one else I talked to had this problem. If you shut down TBPL, as it stands, I won't be able to view try results. I'm hoping it's some weird glitch that will go away by itself, but figured I would file just in case in doesn't.

Thank you for filing :-) This needs to be in the Treeherder component for the relevant people to see it, so moving there now. New relic data data there have been no problems, and it wfm now from abroad (I'm on vacation, but popping in to preform the eol). So it must be something specific to your connection or browser profile. Could you try using: * a new profile * a different browser on the same machine * a different machine/phone/... Thanks!

Restarting my computer seems to have fixed it (thanks, Windows autoupdate-without-warning!).

And now it's happening again. Tested on Firefox, Chrome, and IE, and all of them failed (I'm not sure IE is failing with the same error). However, another computer on the same network works fine. It might be that my computer works after a reboot and starts failing again after hibernation. Clearly the problem is somewhere on my computer, presumably triggered by something different about treeherder from the rest of Mozilla's HTTPS sites. Is there anything different about its configuration or hosting, or is it identical to the other sites? I see it's hosted on what looks like a dedicated IP address.

An easy possible workaround from your side might be to allow non-HTTPS access (possibly under a different domain name). I don't know what the error actually means, but I suspect it's SSL-related. I have no problem with "everything HTTPS" in principle, but it does add another failure point.

Allowing non-https is not something we want to do, since we use persona, it protects against MITMs and even ignoring that, is not worth maintaining another web service just for non-https. We should just figure out what's different about your machine (we've had no other reports of this) and fix that - since this sounds really annoying for you :-) Either way, since this seems machine specific, there's a workaround, and we've not had any other reports of similar behaviour, I think we'll not block tbpl eol on this. Hope this gets figure out soon for you though!

Just an idea Aryeh I wonder if you put your machine on some other network (the inverse of your first test). If it still fails that would re-confirm there is something different about that machine. Have you tried hard-cabling vs. wifi (just curious). Perhaps you could attach a SystemInformation file for Ed/us to check out. AV installed, etc. Another option for that http theory, would be to try dev, at http://treeherder-dev.allizom.org. If it also fails on your machine, then we could exclude https as a cause.

It seems to be working now even after hibernate. Oh well. I'll figure out how to deal with it if it comes up again. Maybe it will just go away. In the worst case I can find another computer to use.