New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 420299 link

Starred by 23 users

Issue metadata

Status: WontFix
Last visit 22 days ago
Closed: Mar 2015
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

issue 390162

Sign in to add a comment

twitter not working

Reported by, Oct 3 2014

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.7 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Go to

What is the expected behavior?
Twitter loads

What went wrong?
This webpage is not available

The webpage at might be temporarily down or it may have moved permanently to a new web address.


Did this work before? Yes Yesterday

Chrome version: 39.0.2171.7  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 15.0 r0

Comment 1 by, Oct 4 2014

It works in other browsers and in incognito.

The same thing happened a few weeks ago -  issue 408944 
Having the same issues. It was doing it prior to this day as well.

Looks like the old SPDY bug is back. Twitter seems to load on initial loading. But then it doesn't allow you to scroll down. And once you refresh after the initial load you either get the error:


or it displays a blank page with the words: Not Found

And if you relaunch in an incognito session, you then end up with the SPDY error:


Can you create an option/switch in Chrome to bypass the SPDY protocol? This is becoming annoying..

tested with the following version, and settings:

Google Chrome	39.0.2171.7 (Official Build) dev-m
Revision	fde783d0141b3de9ba58bca74ad3eb98d9b3c184-refs/branch-heads/2171@{#19}
OS	Windows 
Blink	537.36 (@182806)
JavaScript	V8
User Agent	Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.7 Safari/537.36
Command Line	
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --enable-experimental-app-list --enable-experimental-hotwording --enable-experimental-web-platform-features --enable-extension-action-redesign --google-profile-info --enable-material-design-ntp --enable-nacl --enable-sync-app-list --enable-sync-synced-notifications --ignore-gpu-blacklist --enable-lcd-text --flag-switches-end
Executable Path	C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Profile Path	C:\Users\rgo20641\AppData\Local\Google\Chrome\User Data\Default

Labels: Cr-Internals-Network-SPDY
Could one of you guys upload a net-internals dump?  Instructions here:
Net internals file attached.

Version 39.0.2171.7 dev (64-bit) on Mac
286 KB Download
Both and suggest this is a Twitter server-side issue. However, it's only happening in dev builds of chrome? I've asked my friends, who all run not-dev builds...they aren't experiencing this. 

Version 39.0.2171.7 dev-m (64-bit)
Labels: -Pri-2 Pri-1 M-39
Status: Assigned
If only in dev then this may be an http/2 issue (rather than spdy). 

bnc: Can you look into this?
Seems to be happening in Mac OSX version of Chrome too!
similar bug filed with h2-14 versions of firefox, twitter dev comments over there that its likely a server side update.
39.0.2171.7 on Linux, too. Definitely a protocol thing.

(Similar thing happened a month or so ago, fiddling with disabling SPDY kind of helped.)

Comment 12 by, Oct 10 2014

Labels: -M-39 MovedFrom-39 M-40
Moving all non essential bugs to the next Milestone.

Comment 13 by, Oct 21 2014

Status: Fixed
Issue presumably fixed on Twitter's side, see
Not fixed, this has been a problem for me for over a week now, including the latest Chrome update.  Currently running 40.0.2209.0 dev-m.
+1 not fixed 40.0.2209.0 dev-m (64-bit)

It's probably on Twitter side, though. Reported to Bill Gallagher at
Thanks for reporting.
I just started having this issue with Twitter a few moments ago. I'm running Version 39.0.2171.62 beta (64-bit) incognito.
Screen Shot 2014-11-14 at 9.43.55 AM.png
61.3 KB View Download

Comment 18 by, Nov 17 2014

Status: Started
Labels: -Pri-1 -M-40 M-41 MovedFrom-40 Pri-2
This issue is Pri-1 but has already been moved once, therefore lowering to Pri-2 and moving to next milesone.
This is still happening, quite often. 

Version 41.0.2224.3 dev-m (64-bit)

Comment 21 by, Nov 24 2014

kidyelman:  Thank you for reporting.  While we are working on the problem, you can start Chrome with the --enable-npn-http command line flag, or disable SPDY4 in chrome://flags to work around this issue.
SPDY4 is disabled already in flags. 
Using the command line flag "--use-spdy=off" works for me.

Comment 24 by, Dec 1 2014

Blocking: chromium:390162

Comment 25 by Deleted ...@, Dec 4 2014

Been having this a few times this week on 2 different PCs in 2 different locations - both using Chrome dev (right now at v41.0.2236.0 dev-m) :( 

SPDY4 flag is already disabled.

Have seen this happening a lot with Twitter in the last few months - I thought it was possibly fixed until it returned this week. 

Twitter will load as normal, then when I either:
- Try to post a new tweet (Gives a 500)
- Scroll and reach the end of the page - the 'load more' functionality will die
- Trying to visit someone's profile or navigating away from the homepage will return 'This webpage is not available' and 'The webpage at might be temporarily down or it may have moved permanently to a new web address.' with the Error code: ERR_CONNECTION_CLOSED

Incognito and other browsers (IE11 + Firefox) work with no problems.

Comment 26 by Deleted ...@, Dec 9 2014

512 KB Download
Sometimes I get 404 OK when requesting (and sometimes I get ERR_CONNECTION_CLOSED like everyone else). Is this related to this issue, or something else?
404 OK.png
17.4 KB View Download
The issue went away for a bit, but this has started happening again, I have SPDY disabled in flags; and the previously mentioned npn-http flag in my Chrome target path. running: Version 41.0.2243.0 dev-m (64-bit)
Labels: -M-41 MovedFrom-41
This issue has already been moved once and is lower than Priority 1,therefore removing mstone.
Labels: -Cr-Internals-Network-SPDY Cr-Internals-Network-HTTP2
Migrate from Cr-Internals-Network-SPDY to Cr-Internals-Network-HTTP2
We had two people with a very similar issue here, this morning: it worked yesterday, but today we were getting "net::ERR_CONNECTION_CLOSED".

Chrome 41.0.2272.89 (32-bit), Windows 7, reaching a HTTPS server on `localhost` with a self-signed certificate.

Connection to the same application on its staging and prod environments were successful; we just couldn't connect to our local development machines.

Our server logs didn't show any activity, as if chrome never reached the server.  We suspected a SSL issue.

We found this other page:

Our staging and prod environment used SHA256 certs, but our local dev machines still used SHA1.

We were eventually able to fix our issue by regenerating a self-signed certificate, using SHA256.

If the site certificate is really the issue - which it appears to be - it might be worth fixing this bug, to give users better feedback...  "net::ERR_CONNECTION_CLOSED" wasn't very helpful.

gilbert.dave71:  This issue is for a problem apparently related to talking to Twitter over HTTP/2, which sounds nothing like your issue.  ERR_CONNECTION_CLOSED just means a socket was unexpectedly closed on us (Like if Twitter doesn't like our HTTP/2 frames).

Please file a new bug for the issue you're running into.

Comment 33 by, Mar 31 2015

Status: WontFix
Closing ticket for lack of activity.  If problem persist, feel free to reopen, and please provide net-logs.

Comment 34 by, May 26 2015

Not directly related to twitter but I had pretty much the same issue with my own site while using nginx. The issue is described and fixed at

Comment 35 by, Jun 1 2015

Re: #34.  Thanks for the heads up.  It's always comforting to see a mystery being solved.

Sign in to add a comment