# ModuleStreamResolver HLS 404's unless RTMP client is connected

**URL:** <https://community.wowza.com/t/modulestreamresolver-hls-404s-unless-rtmp-client-is-connected/51756>\
**Category:** Wowza Streaming Engine\
**Created:** [August 7, 2018, 2:04am UTC](https://community.wowza.com/t/modulestreamresolver-hls-404s-unless-rtmp-client-is-connected/51756 "2018-08-07T02:04:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bryan\_Hughes](https://avatars.discourse-cdn.com/v4/letter/b/7ea924/32.png) [@Bryan\_Hughes](https://community.wowza.com/u/Bryan_Hughes)\
**Post date:** [August 7, 2018, 2:04am UTC](https://community.wowza.com/t/modulestreamresolver-hls-404s-unless-rtmp-client-is-connected/51756/1 "2018-08-07T02:04:16Z")

</div>

I’m trying to set my edge servers to use the [ModuleStreamResolver](https://www.wowza.com/docs/how-to-dynamically-resolve-edge-server-stream-requests-to-origin-servers-modulestreamresolver) for service HLS streams but requests for HLS streams will 404 unless there’s an RTMP stream already pulling from the origin.

Also once I get an HLS stream after starting an RTMP stream the HLS stream will 404 after a minute or so if the RTMP stream is shut down.

Since I’m using the [ModuleStreamResolver](https://www.wowza.com/docs/how-to-dynamically-resolve-edge-server-stream-requests-to-origin-servers-modulestreamresolver) to dynamically pull streams from various edges with varying stream names, I don’t know the stream locations ahead of time to set up start-up streams, as mentioned [here](http://community.wowza.com/community/questions/7862/mpeg-dash-live-repeater-reply-with-404-response.html#answer-16321).

Is this expected behavior or am I missing something to start the packetizers on requests for HLS?