# Wowza player does not reconnect in Chrome on PC when source temporarily disconnects.

**URL:** <https://community.wowza.com/t/wowza-player-does-not-reconnect-in-chrome-on-pc-when-source-temporarily-disconnects/178>\
**Category:** Wowza Player\
**Created:** [December 8, 2016, 5:32pm UTC](https://community.wowza.com/t/wowza-player-does-not-reconnect-in-chrome-on-pc-when-source-temporarily-disconnects/178 "2016-12-08T17:32:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/system/32/447_2.png) [@system](https://community.wowza.com/u/system)\
**Post date:** [December 8, 2016, 5:32pm UTC](https://community.wowza.com/t/wowza-player-does-not-reconnect-in-chrome-on-pc-when-source-temporarily-disconnects/178/1 "2016-12-08T17:32:03Z")

</div>

I read in your notes there is a buffering issue with Chrome on an Android.

I have come across the same with Chrome on a PC on certain live streams.

Also, when there is a disconnection at source, when it resumes, the stream does not automatically re-connect and we get the egg-timer with the message “The live event has ended”.

That means one has to guarantee perfect broadcast bandwidth or viewers will think the broadcast has ended - not practical in third-world countries.

Using GetCurrent State in the API gives the following messages when there is a temporary disconnect:

playing

playback complete

ready-to-play

But although it says ready to play and the stream it is expecting is playing, it does not reconnect - in Windows Chrome at least.

ys

---

<div class="post-metadata">

**Author:** ![alan\_costello](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@alan\_costello](https://community.wowza.com/u/alan_costello)\
**Post date:** [January 14, 2017, 12:10am UTC](https://community.wowza.com/t/wowza-player-does-not-reconnect-in-chrome-on-pc-when-source-temporarily-disconnects/178/2 "2017-01-14T00:10:45Z")

</div>

I found this is due to using the non-flash wowza player in the browser.

With force flash (“useFlash”:true) poor quality streams play much, much better.

Because I have a few poor quality streams I now force flash on any browsers (the wowza player falls back to non-flash player if necessary).

I was wanting to be Flash Free, but it is not practical yet, and this player is still a step up with inline Android playback and decent vod playback (I still force flash there also - the non-flash player is more particular about formats).

And the player does provide non-flash playback in browsers if need be.