Tvheadend

https://www.websocket.org/echo.html
browser work fine

saen acro wrote:

Only EPG page show and after few seconds page reload

Me too! With Chrome Browser... only EPG shows.

So, I rollback to the previous snapshot before this change: http://www.tvheadend.org/projects/tvheadend/repository/revisions/f9df9b7401e1838767c0e55126fae7d39640db9a

+1

Mono Polimorph wrote:

saen acro wrote:

Only EPG page show and after few seconds page reload

Me too! With Chrome Browser... only EPG shows.

So, I rollback to the previous snapshot before this change: http://www.tvheadend.org/projects/tvheadend/repository/revisions/f9df9b7401e1838767c0e55126fae7d39640db9a

I am using reverse proxy with apache and tvheadend; in this situation the problem still exists.

But accessing from the local-area-network without proxy, everything is fine.

Do I have to change my config somehow to ensure tvheadend is accessible through the reverse proxy?

You should configure websockets proxy, too.

i'm on v4.3-333-g08c4069
WebSocket connection to 'ws://192.168.0.254:9981/comet/ws' failed: Connection closed before receiving a handshake response

using chromium 60.0.3112.101 64 bits

using any other browser (ff, ie, chrome) also fails

(/) Firefox latest 32/64bit no problem
(/) Opera latest no problem
(/) Vivaldi latest no problem
(/) EDGE and IE 11 no problem

saen acro wrote:

(/) Firefox latest 32/64bit no problem
(/) Opera latest no problem
(/) Vivaldi latest no problem
(/) EDGE and IE 11 no problem

(/) Chromium 60.0.3112.78 (Developer Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit) - No problem here..

Request URL:ws://192.168.1.3:9981/comet/ws
Request Method:GET
Status Code:101 Switching Protocols
Response Headers
view source
Connection:Upgrade
Sec-WebSocket-Accept:<redacted>
Sec-WebSocket-Protocol:tvheadend-comet
Upgrade:websocket