# Securing the edge - Relaying abuse

**URL:** <https://community.wowza.com/t/securing-the-edge-relaying-abuse/35494>\
**Category:** Wowza Streaming Engine\
**Created:** [June 5, 2014, 7:47am UTC](https://community.wowza.com/t/securing-the-edge-relaying-abuse/35494 "2014-06-05T07:47:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jan\_Roth](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@Jan\_Roth](https://community.wowza.com/u/Jan_Roth)\
**Post date:** [June 5, 2014, 7:47am UTC](https://community.wowza.com/t/securing-the-edge-relaying-abuse/35494/1 "2014-06-05T07:47:05Z")

</div>

Hello!

We have a wowza-edge-server 3.1.2, which is abused as a rtmp - relay server.

The module ModuleRTMPAuthenticate is installed and working.

StreamNameAlias is installed and it seems to be working.

URLs which hit our server look like this one:

rtmp://ourstreamserver.com/liveedge//rtmp://differentServer/live/somemountppoint

The URLs are redirected by our server and sadly - they are working: how can we avoid this?

Thanks for help!

Jan

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [June 6, 2014, 1:18am UTC](https://community.wowza.com/t/securing-the-edge-relaying-abuse/35494/2 "2014-06-06T01:18:48Z")

</div>

If you make the StreamType “live” and start the streams you want on the edge(s) using StartUpStreams with MediaCaster type “liverepeater”, then this can’t happen. Alternatively, as you have StreamNameAlias in place, you can limit what will work in the play alias file by adding allowed rules and removing the default rule.

Richard