# Player.twitch.tv refused to connect

**URL:** <https://discuss.dev.twitch.com/t/player-twitch-tv-refused-to-connect/26441>\
**Category:** API\
**Created:** [June 16, 2020, 1:59pm UTC](https://discuss.dev.twitch.com/t/player-twitch-tv-refused-to-connect/26441 "2020-06-16T13:59:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [June 16, 2020, 3:30pm UTC](https://discuss.dev.twitch.com/t/player-twitch-tv-refused-to-connect/26441/4 "2020-06-16T15:30:59Z")

</div>

> [@Twitch Embedded Player Updates in 2020](https://discuss.dev.twitch.com/t/twitch-embedded-player-updates-in-2020/23956/1):
>
> **Update (2020/05/13):** These changes will go into effect on **June 10, 2020** and has been announced on [this post](https://discuss.dev.twitch.com/t/twitch-embedded-player-migration-timeline-update/25588). Please review the action steps below to understand how to update your iframe and JavaScript embeds by this date.

June 10th

> [@Twitch Embedded Player Updates in 2020](https://discuss.dev.twitch.com/t/twitch-embedded-player-updates-in-2020/23956/120):
>
> ## Local development
> 
> - Use “localhost” or any IP address in the “127.0.0.1/8” range as the parent value to use either HTTP or HTTPS in local development. Any port can be used, though this does not need to be specified anywhere (80, 3000, 8100, etc)
> - Local development over other IP ranges (e.g. 192.1.1.1) must adhere to the HTTPS requirement, though a valid certificate is not required

localhost is exempt from this to allow testing/development

---

_[View the full topic](https://discuss.dev.twitch.com/t/player-twitch-tv-refused-to-connect/26441)._