# MPEG DASH live repeater reply with 404 response
**URL:** https://community.wowza.com/t/mpeg-dash-live-repeater-reply-with-404-response/47404
**Category:** Wowza Streaming Engine
**Created:** [October 17, 2016, 6:18pm UTC](https://community.wowza.com/t/mpeg-dash-live-repeater-reply-with-404-response/47404 "2016-10-17T18:18:42Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Streaming\_Engineer](https://community.wowza.com/u/Streaming_Engineer)
#### Post date: [October 17, 2016, 6:18pm UTC](https://community.wowza.com/t/mpeg-dash-live-repeater-reply-with-404-response/47404/1 "2016-10-17T18:18:42Z")
Hi,
I setup wowza origin - edge pull for live streaming. I have configured wowza with the following:
**Origin**
- Application Type: Live
- Playback Types: MPEG-DASH, Apple HLS and Adobe RTMP
- Options: Low-latency stream (ideal for chat applications) and Cross-origin resource sharing (CORS) (for HTTP-based streams)
- **Edge**
- Application Type: Live Edge
- Playback Types: MPEG-DASH, Apple HLS and Adobe RTMP
- Options: Low-latency stream (ideal for chat applications) and Cross-origin resource sharing (CORS) (for HTTP-based streams)
- Primary Origin URL: wowz://origin:1935/originapp
- Input stream is RTMP stream published to originapp rtmp://origin:1935/originapp/test. It outputs on the edge side:
- RTMP rtmp://edge:1935/edgeapp/test
- HLS [http://edge/edgeapp/test/playlist.m3u8](http://edge/edgeapp/test/playlist.m3u8)
- MPEG-DASH [http://edge/edgeapp/test/manifest.mpd](http://edge/edgeapp/test/manifest.mpd)
- RTMP and HLS streams on the edge are working. But MPEG-DASH output give HTTP 404 at the first request attempt. First attempt also takes about 11-12 seconds to get reply from wowza. I wonder if there is any config to avoid 404 response for MPEG-DASH when the stream is fresh (not pulled) on the edge and how to improve the delay 11-12 seconds. I think HLS repeater has similar mechanism with DASH right? But the problem doesn’t happen with HLS.
---
### Author:  [@Andrew\_Ramberg](https://community.wowza.com/u/Andrew_Ramberg)
#### Post date: [December 20, 2016, 12:04pm UTC](https://community.wowza.com/t/mpeg-dash-live-repeater-reply-with-404-response/47404/2 "2016-12-20T12:04:53Z")
Hello,
You might want to ensure that the stream is active by setting up a Startup Stream. This should keep the packetizers active and reduce the delay sometimes seen after the stream is first connected.
Another thing you could do is adjust your DASH packetizer settings to lower values to lower the time required for the initial 3 chunks to be created. See the following article for more information:
[How to configure MPEG-DASH packetization](https://www.wowza.com/docs/how-to-configure-mpeg-dash-packetization-mpegdashstreaming%28mpegdashstreaming%29#mgrlive)
You could try adjusting to the following suggested settings:
mpegdashChunkDurationTarget (3000)
mpegdashPlaylistChunkCount (3)
mpegdashRepeaterChunkCount (3)
Best regards,
Andrew