Notary Connectivity Failure on Windows Client

[JeremyRand]

Notaries work fine for me from a Linux client, but when I run the client in Windows 8, I frequently get "Connectivity Failure" reported by Firefox. In cases where this happens, the notary server's debug output says that it received no connections. Often it works for a particular site after I refresh about 10 times (in which case the cert is cached, the server does report a connection, and that site works until I clear the client cert cache).

Any idea what might cause this?

[mk-fg]

No, don't know what it might be.

I'd try running wireshark or something like that, see if there're any attempts to establish connection to notary host (and what's being passed there) - might be some TLS error that isn't logged by twisted, I guess.

And debug output from convergence (if you run ff from cmd.exe terminal, enabling convergence logging in about:config or in Logging.js file) should show what convergence thinks is happening there.

Might also be some uncaught js error in Firefox JS Console.

I know convergence doesn't work in firefox 31+ (have been running it from aurora for a while), but don't think it's the same symptoms there, and it shouldn't yet be released as stable, I guess.