502 response to XHR while connected using the PIA browser extension

[thegrumble]

While attempting to look into connection issues that happen when connecting using the PIA chrome extension (ID jplnlifepflhkbkgonidnobkakhmpnmh, version 1.5.10), one of the XHRs returned a 502 while the connection was just sitting in a nearly-empty idle channel.

JS console log: https://gist.github.com/xnrand/694dd1bf2563417ddcba74144680f528#file-kiwi-freenode-net-1529522730656-log

[prawnsalad]

@tomaw could you check your access logs to see if you have any upstream errors? (excluding timeouts as they're expected with longpolling)

@xnrand does this work without using PIA? If it does, is it using a websocket or more of the polling?

[thegrumble]

When not using the PIA extension, it works fine and it uses websockets.
It is my understanding that the PIA extension does not support websockets, which is why it falls back to the XHR method and XHR fails somewhere.

[prawnsalad]

I believe this has fixed itself now so I'll close this issue. I can only assume that there was some PIA proxy weirdness going on at the time.

[thegrumble]

Having just tried it again, the exact same thing happens after about a minute of idling.

In case someone wants to look up a logged error:
Error 502 Ray ID: 43544f3698225480 • 2018-07-04 20:23:24 UTC

Edit: reproduced from multiple PIA exit destinations:

• Spain – 43544f3698225480 • 2018-07-04 20:23:24 UTC
• UK London – 4354598f5c273470 • 2018-07-04 20:30:27 UTC
• CA Montreal – 435474f17d9f3f7d • 2018-07-04 20:49:09 UTC

[prawnsalad]

@xnrand could you try to reproduce this at https://kiwiirc.com/nextclient/irc.freenode.net/#test ?

[thegrumble]

I cannot reproduce it because on kiwiirc.com, the browser with the PIA extension uses a websocket, while on kiwi.freenode.net, the websocket fails with net::ERR_NOT_IMPLEMENTED.

I have absolutely no clue why that happens.