a glitch perhaps...?

Bad_azz

Well-Known Member
Charter Member
Cager
Joined
Jul 16, 2016
Messages
3,196
I've been getting this a lot when I try to load the forum - via chrome using my mac mini.
it could just be because of a crappy signal perhaps- but it isn't the norm , it has only started since the twitter link- could there be some connection to that- not that I use the twitter or fb pages for the forum.


"This site can’t be reached

The web page at https://forum.expatindo.org/ might be temporarily down or it may have moved permanently to a new web address.

ERR_SPDY_PROTOCOL_ERROR"
 

El_Goretto

Moderator
Moderator
Cager
Joined
Jul 13, 2016
Messages
2,694
I've been having this error which I fixed by copy pasting this in the address bar:

Code:
chrome://net-internals/#events&q=type:SPDY_SESSION%20is:active

Then pressing enter.

Then find and click "Flush Sockets".

Reload the forum and it should work again.
 

Bad_azz

Well-Known Member
Charter Member
Cager
Joined
Jul 16, 2016
Messages
3,196
nice to know it isn't just me . Thank you.
 

Nasigan

Active Member
Charter Member
Cager
Joined
Jul 24, 2016
Messages
129
I've been getting this a lot when I try to load the forum - via chrome using my mac mini.
it could just be because of a crappy signal perhaps- but it isn't the norm , it has only started since the twitter link- could there be some connection to that- not that I use the twitter or fb pages for the foru

"This site can’t be reached

The web page at https://forum.expatindo.org/ might be temporarily down or it may have moved permanently to a new web address.

ERR_SPDY_PROTOCOL_ERROR"
the same here, many2 times, very frustrating, I try all kind of things but still the same, the last times was yesterday afternoon.( I use Android tablet)
 

Bad_azz

Well-Known Member
Charter Member
Cager
Joined
Jul 16, 2016
Messages
3,196
This is only happening with the forum, no other sites that I use, such as email, facebook, news channels, etc.
 

Bad_azz

Well-Known Member
Charter Member
Cager
Joined
Jul 16, 2016
Messages
3,196
not today... :) will let you know if it does it again.
 

Theoros

New Member
Joined
Jul 26, 2017
Messages
24

El_Goretto

Moderator
Moderator
Cager
Joined
Jul 13, 2016
Messages
2,694
The SPDY protocol was deprecated by Google in favor of HTTP/2, and Nginx has followed suit, superseding their buggy ngx_http_spdy_module with ngx_http_v2_module. I recommend removing the former and installing/enabling the latter.

Browser support for SPDY is going away as well. Google Chrome dropped support for SPDY in version 51 and Firefox dropped it in version 50.

Thank you for your input!

Our server does not use SPDY and is already using HTTP/2. However, Chrome still reports the error as being SPDY when in fact it could very well be an HTTP/2 error. (Chrome hasn't updated the error messages since dropping support for SPDY).

So I'm confident that it isn't an SPDY issue but maybe something to do with mod_pagespeed (currently being upgraded), https configuration or nginx configuration.

Do you have another idea of what it could be maybe?

Upgrading to Chrome 51 or newer should make the problem go away on your end.

I also have the bug and I use latest Chrome version. In fact, I got the bug on both Chrome for Android and PC.
 

El_Goretto

Moderator
Moderator
Cager
Joined
Jul 13, 2016
Messages
2,694
It just did it again :(

If that's the case, I'm going to try a fix. Please report if it happens again!

For those interested in the details, we will turn off mod_pagespeed while our host is upgrading it.
 

Theoros

New Member
Joined
Jul 26, 2017
Messages
24
However, Chrome still reports the error as being SPDY when in fact it could very well be an HTTP/2 error. (Chrome hasn't updated the error messages since dropping support for SPDY).

This is the kind of inconsistency that frustrates me about Chrome development practices, but that's a tangent I won't get into.

So I'm confident that it isn't an SPDY issue but maybe something to do with mod_pagespeed (currently being upgraded), https configuration or nginx configuration.

Do you have another idea of what it could be maybe?

After digging into related Chrome and Nginx bug reports this looks like a real slippery error to pin down, made worse by Chrome's ERR_SPDY_PROTOCOL_ERROR acting as somewhat of a catch-all. But PageSpeed looks like a big minefield so I would probably treat it as the prime suspect. I've never used it so I have no informed ideas on debugging. If disabling it gets rid of the error I do recommend filing a bug.

Apart from PageSpeed, one ERR_SPDY_PROTOCOL_ERROR trigger condition reported by multiple people that sticks out to me is the presence of HTTP headers that Chrome under certain conditions seems to handle less gracefully than other browsers. This person reports Chrome doesn't like the X-Frame-Options header with HTTP/2 and SSL, and I noticed that's present among the forum's current headers. Another person found a culprit (also here) in malformed headers being passed to the server from their PHP code, which could imply a XenForo bug is involved.
 

El_Goretto

Moderator
Moderator
Cager
Joined
Jul 13, 2016
Messages
2,694
Thank you for the insight @Theoros!

I'll forward this to our host to help then pinpoint. Being on a shared server, I have little direct control over its configuration.
 

Users who viewed this discussion (Total:0)

Follow Us

Latest Expat Indo Articles

Latest Activity

New posts Latest threads

Latest Tweets by Expat Indo

Online Now

No members online now.

Newest Members

Forum Statistics

Threads
4,835
Messages
73,943
Members
2,154
Latest member
SwingNinja
Top Bottom