# Can't access to wowza web manager

**URL:** <https://community.wowza.com/t/cant-access-to-wowza-web-manager/95785>\
**Category:** Wowza Streaming Engine\
**Created:** [January 5, 2023, 8:43am UTC](https://community.wowza.com/t/cant-access-to-wowza-web-manager/95785 "2023-01-05T08:43:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adrian\_Francis](https://avatars.discourse-cdn.com/v4/letter/a/4bbf92/32.png) [@Adrian\_Francis](https://community.wowza.com/u/Adrian_Francis)\
**Post date:** [January 5, 2023, 8:43am UTC](https://community.wowza.com/t/cant-access-to-wowza-web-manager/95785/1 "2023-01-05T08:43:16Z")

</div>

Hello!  
Before new year we’ve updated our streamlock certificate. And yesterday we’ve found out, that web manager is not accessible.

I’ve updated WowzaStreamingEngine from 4.8.13 to 4.8.20 today. Still not working.  
Here are some info:

Server configuration:

> ```
> <?xml version="1.0" encoding="UTF-8"?>
> <Root version="2">
> <Server>
> <Name>Wowza Streaming Engine</Name>
> <Description>Wowza Streaming Engine is robust, customizable, and scalable server software that powers reliable streaming of high-quality video and audio to any device, anywhere.</Description>
> <RESTInterface>
> <Enable>true</Enable>
> <IPAddress>*</IPAddress>
> <Port>8087</Port>
> <!-- none, basic, digest, remotehttp, digestfile -->
> <AuthenticationMethod>digest</AuthenticationMethod>
> <DiagnosticURLEnable>true</DiagnosticURLEnable>
> <SSLConfig>
> <Enable>false</Enable>
> <KeyStorePath></KeyStorePath>
> <KeyStorePassword></KeyStorePassword>
> <KeyStoreType>JKS</KeyStoreType>
> <SSLProtocol>TLS</SSLProtocol>
> <Algorithm>SunX509</Algorithm>
> <CipherSuites></CipherSuites>
> <Protocols></Protocols>
> </SSLConfig>
> <IPWhiteList>*</IPWhiteList>
> <IPBlackList></IPBlackList>
> <EnableXMLFile>false</EnableXMLFile>
> <DocumentationServerEnable>false</DocumentationServerEnable>
> <DocumentationServerPort>8089</DocumentationServerPort>
> <!-- none, basic, digest, remotehttp, digestfile -->
> <DocumentationServerAuthenticationMethod>digest</DocumentationServerAuthenticationMethod>
> <Properties>
> </Properties>
> </RESTInterface>
> <CommandInterface>
> <HostPort>
> <ProcessorCount>${com.wowza.wms.TuningAuto}</ProcessorCount>
> <IpAddress>*</IpAddress>
> <Port>8083</Port>
> </HostPort>
> </CommandInterface>
> <AdminInterface>
> <!-- Objects exposed through JMX interface: Server, VHost, VHostItem, Application, ApplicationInstance, MediaCaster, Module, Client, MediaStream, SharedObject, Acceptor, IdleWorker -->
> <ObjectList>Server,VHost,VHostItem,Application,ApplicationInstance,MediaCaster,Module,IdleWorker</ObjectList>
> </AdminInterface>
> <Stats>
> <Enable>true</Enable>
> <Properties>
> <Property>
> <Name>statsManagerDebugEnable</Name>
> <Value>false</Value>
> <Type>Boolean</Type>
> </Property>
> <Property>
> <Name>statsDatabaseManagerDebugEnable</Name>
> <Value>false</Value>
> <Type>Boolean</Type>
> </Property>
> </Properties>
> </Stats>
> <!-- JMXUrl: service:jmx:rmi://localhost:8084/jndi/rmi://localhost:8085/jmxrmi -->
> <JMXRemoteConfiguration>
> <Enable>false</Enable>
> <IpAddress>localhost</IpAddress>
> <!-- set to localhost or internal ip address if behind NAT -->
> <RMIServerHostName>localhost</RMIServerHostName>
> <!-- set to external ip address or domain name if behind NAT -->
> <RMIConnectionPort>8084</RMIConnectionPort>
> <RMIRegistryPort>8085</RMIRegistryPort>
> <Authenticate>true</Authenticate>
> <PasswordFile>${com.wowza.wms.ConfigHome}/conf/jmxremote.password</PasswordFile>
> <AccessFile>${com.wowza.wms.ConfigHome}/conf/jmxremote.access</AccessFile>
> <SSLSecure>false</SSLSecure>
> </JMXRemoteConfiguration>
> <UserAgents>Shockwave Flash|CFNetwork|MacNetwork/1.0 (Macintosh)</UserAgents>
> <Streams>
> <DefaultStreamPrefix>mp4</DefaultStreamPrefix>
> </Streams>
> <ServerListeners>
> <ServerListener>
> <BaseClass>com.wowza.wms.mediacache.impl.MediaCacheServerListener</BaseClass>
> </ServerListener>
> <!--
> <ServerListener>
> <BaseClass>com.wowza.wms.plugin.loadbalancer.ServerListenerLoadBalancerListener</BaseClass>
> </ServerListener>
> -->
> <!--
> <ServerListener>
> <BaseClass>com.wowza.wms.plugin.loadbalancer.ServerListenerLoadBalancerSender</BaseClass>
> </ServerListener>
> -->
> </ServerListeners>
> <VHostListeners>
> <!--
> <VHostListener>
> <BaseClass></BaseClass>
> </VHostListener>
> -->
> </VHostListeners>
> <HandlerThreadPool>
> <PoolSize>${com.wowza.wms.TuningAuto}</PoolSize>
> </HandlerThreadPool>
> <TransportThreadPool>
> <PoolSize>${com.wowza.wms.TuningAuto}</PoolSize>
> </TransportThreadPool>
> <RTP>
> <DatagramStartingPort>6970</DatagramStartingPort>
> <DatagramPortSharing>false</DatagramPortSharing>
> </RTP>
> <Manager>
> <!-- Properties defined are used by the Manager -->
> <Properties>
> </Properties>
> </Manager>
> <Transcoder>
> <PluginPaths>
> <QuickSync></QuickSync>
> </PluginPaths>
> </Transcoder>
> <!-- Properties defined here will be added to the IServer.getProperties() collection -->
> <Properties>
> </Properties>
> </Server>
> </Root>
> 
> ```

Opened ports:

> ```
> ubuntu@xxx:/usr/local/WowzaStreamingEngine/conf$ sudo netstat -tunlp
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
> tcp 0 0 0.0.0.0:1998 0.0.0.0:* LISTEN 1234/nginx: master
> tcp 0 0 0.0.0.0:1935 0.0.0.0:* LISTEN 6838/java
> tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 6838/java
> tcp 0 0 0.0.0.0:38613 0.0.0.0:* LISTEN 6838/java
> tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 888/systemd-resolve
> tcp 0 0 0.0.0.0:8086 0.0.0.0:* LISTEN 6838/java
> tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1201/sshd
> tcp 0 0 0.0.0.0:8087 0.0.0.0:* LISTEN 6838/java
> tcp 0 0 0.0.0.0:8088 0.0.0.0:* LISTEN 6877/java
> tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 6838/java
> tcp6 0 0 :::22 :::* LISTEN 1201/sshd
> udp 0 0 127.0.0.53:53 0.0.0.0:* 888/systemd-resolve
> udp 0 0 0.0.0.0:68 0.0.0.0:* 901/dhclient
> 
> ```

Sever status:

> ubuntu@xxx:/usr/local/WowzaStreamingEngine/conf$ sudo systemctl status WowzaStreamingEngine  
> ● WowzaStreamingEngine.service - WowzaStreamingEngine  
> Loaded: loaded (/usr/lib/systemd/system/WowzaStreamingEngine.service; enabled; vendor preset: enabled)  
> Active: active (running) since Thu 2023-01-05 08:16:51 UTC; 21min ago  
> Main PID: 6779 (systemd.sh)  
> Tasks: 335 (limit: 4915)  
> CGroup: /system.slice/WowzaStreamingEngine.service  
> ├─6779 /bin/bash /usr/local/WowzaStreamingEngine/bin/systemd.sh start  
> └─6838 java -Xmx11204M -XX:+UseG1GC -XX:MaxGCPauseMillis=100 -XX:SurvivorRatio=1 -server -Djava.net.preferIPv

WowzaStreamingEngineManager is running too.

Any suggestions?

Thanks!

---

<div class="post-metadata">

**Author:** ![Tim\_Dougherty](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/tim_dougherty/32/596_2.png) [@Tim\_Dougherty](https://community.wowza.com/u/Tim_Dougherty)\
**Post date:** [January 10, 2023, 12:50am UTC](https://community.wowza.com/t/cant-access-to-wowza-web-manager/95785/2 "2023-01-10T00:50:05Z")

</div>

Did you get this figured out?

Be sure to check your Wowza Streaming Engine Manager (WSEM) configuration, following the upgrade: `[install-dir]/manager/conf/tomcat.properties` to be sure mapping to your [streamlock.net](http://streamlock.net) certificate is intact.

It appears that you have strong familiarity with network port management, but reviewing your WSEM config would be a good start. Also, make sure the WowzaStreamingEngineManager service is running.

If you’re still wrestling with this, get in touch with our Support Team:

**Open a Support Ticket** - [https://www.wowza.com/support/open-ticket](https://www.wowza.com/support/open-ticket)