=== wgrant changed the topic of #launchpad to: Help contact: guruprasad (Indian Standard Time UTC+0530 hrs Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad [01:59] The build queue has finally caught up. [02:00] \o/ [20:21] launchpad.net didn’t send any data. [20:21] Cannot log in [20:21] bugs.launchpad.net didn’t send any data. [20:22] or even get the damned thing to load [20:22] working fine here; maybe try mtr to try to spot problems? [20:23] 0% packet loss [20:24] it's not like it's uncommon [20:26] hmm... "didn't send any data" sounds vaguely familiar -- any chance this is firefox with privacy badger? I kept getting errors like that on discourse sites (never launchpad, though) back when I used to use privacy badger [20:27] Nope. Chrome. [20:28] heh turns out my memory was pretty poor, it was saying protocol violation.. https://bugzilla.mozilla.org/show_bug.cgi?id=1716898 [20:28] Mozilla bug 1716898 in Core "Firefox experiences Network Protocol Violation on Discourse based Websites" [--, Resolved: Incomplete] [20:30] trying to log in is where the problem starts, apparently. after that every request fails. [20:40] cookie errors [20:40] This cookie was blocked because its path was not an exact match for a superdirectory of the requests url's path. [20:40] This cookie was blocked because neither did the request URL's domain exactly match the cookie's domain, nor was the request URL's domain a subdomain of the cookie's Domain attribute value. [20:44] So it's setting invalid cookies [21:05] All looks fine here. launchpad.net sets a cookie with Domain: .launchpad.net, which is valid [21:07] Just tried in Chrome 101.0.4951.64 in an incognito window to make sure I was logging in from scratch; all fine