# WSE and WSE Manager Locked Down to SSL Only

**URL:** <https://community.wowza.com/t/wse-and-wse-manager-locked-down-to-ssl-only/54215>\
**Category:** Wowza Streaming Engine\
**Created:** [November 20, 2019, 3:49pm UTC](https://community.wowza.com/t/wse-and-wse-manager-locked-down-to-ssl-only/54215 "2019-11-20T15:49:55Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Rich\_Sokol](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Rich\_Sokol](https://community.wowza.com/u/Rich_Sokol)\
**Post date:** [November 20, 2019, 3:49pm UTC](https://community.wowza.com/t/wse-and-wse-manager-locked-down-to-ssl-only/54215/1 "2019-11-20T15:49:55Z")

</div>

I am having some challenges getting WSE and WSE Manger to serve only over SSL. We are an enterprise environment where this is mandated. I’ve imported our own certificates, in JKS format, made sure they are readable and correct. Enabled StreamLock. Modified the tomcat.properties file. Modified the startmgr.sh file. By default WSE Manger serves on 8088, but even after making the above config changes, it still renders, kind of. AKA it renders but you can not authenticate? Is this functioning as intended? Also, I am having issues getting SSL working on our other two implementations. Are there documented steps provided by Wowza that detail how to implement SSL across the board? For streaming we can force this via our ELB and/or F5, but I dont feel like we are doing it 100% correct. I dont fully understand how in the Host Ports section in WSE Manager, the out of the box ports are 1935 and 8086, when the Manger serves over 8088 out of the box, and then suggested to serve via 8090 once SSL enabled? Thanks in advance!

---

_[View the full topic](https://community.wowza.com/t/wse-and-wse-manager-locked-down-to-ssl-only/54215)._