# Lots of time, wowza cloud does not accept stream

**URL:** <https://community.wowza.com/t/lots-of-time-wowza-cloud-does-not-accept-stream/49347>\
**Category:** Wowza Video (Formerly Streaming Cloud)\
**Created:** [August 3, 2017, 2:21pm UTC](https://community.wowza.com/t/lots-of-time-wowza-cloud-does-not-accept-stream/49347 "2017-08-03T14:21:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Denton\_Woods](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@Denton\_Woods](https://community.wowza.com/u/Denton_Woods)\
**Post date:** [August 3, 2017, 2:21pm UTC](https://community.wowza.com/t/lots-of-time-wowza-cloud-does-not-accept-stream/49347/1 "2017-08-03T14:21:53Z")

</div>

Hi,

I am using rest Api for cloud live stream. When i try to upload rtmp stream, lots of time, wowza cloud does not accept stream. I am waiting up to 20 seconds after channel start but still having same issue. Please guide to resolve this issue.

---

<div class="post-metadata">

**Author:** ![Jermaine\_Hemby](https://avatars.discourse-cdn.com/v4/letter/j/82dd89/32.png) [@Jermaine\_Hemby](https://community.wowza.com/u/Jermaine_Hemby)\
**Post date:** [August 19, 2017, 5:30pm UTC](https://community.wowza.com/t/lots-of-time-wowza-cloud-does-not-accept-stream/49347/2 "2017-08-19T17:30:36Z")

</div>

Hello,

Thanks for contacting the Wowza Community.

I would suggest opening a ticket [HERE](https://www.wowza.com/support/open-ticket) and explaining this issue. Also include the APIs you are using and we can take a look at the logs to see why the delay is occurring.

regards,

Jermaine

---

<div class="post-metadata">

**Author:** ![Kristeen\_Wurtele](https://avatars.discourse-cdn.com/v4/letter/k/ea666f/32.png) [@Kristeen\_Wurtele](https://community.wowza.com/u/Kristeen_Wurtele)\
**Post date:** [January 21, 2018, 5:26am UTC](https://community.wowza.com/t/lots-of-time-wowza-cloud-does-not-accept-stream/49347/3 "2018-01-21T05:26:44Z")

</div>

@Denton Woods

Did you ever get a resolution here? We’re experiencing the same delay.

---

<div class="post-metadata">

**Author:** ![Landon\_Alder](https://avatars.discourse-cdn.com/v4/letter/l/3ec8ea/32.png) [@Landon\_Alder](https://community.wowza.com/u/Landon_Alder)\
**Post date:** [January 22, 2018, 5:56pm UTC](https://community.wowza.com/t/lots-of-time-wowza-cloud-does-not-accept-stream/49347/4 "2018-01-22T17:56:21Z")

</div>

I’m having this issue as well. I’ve tried waiting 15 seconds after the stream changes status to ‘started’ and I still sometimes have my connection refused with the error: “An error occurred when trying to connect to host: http://{stream url here}” (code 14)

---

<div class="post-metadata">

**Author:** ![Mac\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/mac_hill/32/434_2.png) [@Mac\_Hill](https://community.wowza.com/u/Mac_Hill)\
**Post date:** [January 26, 2018, 5:02pm UTC](https://community.wowza.com/t/lots-of-time-wowza-cloud-does-not-accept-stream/49347/5 "2018-01-26T17:02:31Z")

</div>

Hello,

The actual issue you are running into is DNS propagation. When a livestream is first created and started, a hostname and IP address is automatically assigned. However, I have seen cases where a newly created live stream instance takes some time before the DNS entry propagates for some ISPs.

We generally recommend as part of user’s API workflow to use a resource pool of pre-created/configured live stream instances that are ready to be started. This cuts down on your wait time considerably. I also recommend putting in place logic in your API workflow that checks if the hostname is resolving properly, and only then to allow the broadcast to start.

To verify this, start up an instance that you had previously created (instead of creating a new one), and make a note of the time it takes for the hostname to resolve.

For more information on creating a resource pool:  
[https://www.wowza.com/docs/wowza-streaming-cloud-rest-api-limits#pool](https://www.wowza.com/docs/wowza-streaming-cloud-rest-api-limits#pool)

Please note, we are working on a v1.1 of the API which will return the IP address of the transcoder once it has started to begin streaming to it before the DNS propagation sometime in February of this year.

I hope this clarifies/helps.

Regards,

Mac
