Diagnosing Management Console Proxy Issue - Wiki
Wiki
Diagnosing Management Console Proxy Issue
Errors and Symptoms #
- When accessing the management console, an Apache error page comes up indicating there is a "Proxy Error"
Applicable Versions #
- 2.5.X
Solution #
This message usually indicates that the Apache service on the machine is having trouble proxying the HTTP connection to the Management Console which runs as a Jetty-based service. The first thing to determine is to see if the Management Console itself is fine.
Get access to the server hosting the Management Console. From the desktop, open a browser window and try going to http://localhost:8080/cuaeadmin. If the Managment Console does not come up, then Apache is not configured correctly to proxy the connection.
Open the file C:\Program Files\Cisco Systems\Unified Application Environment\System\Apache\conf\cuaeadmin.conf.
The following should be the contents of the file:
<IfModule !mod_headers.c>
LoadModule headers_module modules/mod_headers.so
</IfModule>
<IfModule !mod_proxy.c>
LoadModule proxy_module modules/mod_proxy.so
</IfModule>
<IfModule !mod_rewrite.c>
LoadModule rewrite_module modules/mod_rewrite.so
</IfModule>
ProxyRequests Off
ProxyPass /cuaeadmin http://localhost:8080/cuaeadmin
ProxyPass /cuaeadmin/ http://localhost:8080/cuaeadmin
ProxyPassReverse /cuaeadmin http://localhost:8080/cuaeadmin
<Directory proxy:http://localhost:8080>
Options Indexes FollowSymLinks
AllowOverride none
Order allow,deny
Allow from all
</Directory>If that is fine, then you should try looking at the Apache error logs and see if there is any noticable error messages. Contact Cisco Technical Support or try the Developer Forums for help.
If the Management Console does not even come in the web browser, then go check Windows Services to see whether or not the "CUAE Management Service" is running.
- If it is running, check to see and make sure that there is nothing else running on the machine that could be using and blocking port 8080.
- If it is not running, try and start the service.
- If the service won't run, then look at the service wrapper log found in C:\Program Files\Cisco Systems\Unified Application Environment\MgmtServiceLauncher\logs\wrapper.log and contact Cisco Technical Support or try the Developer Forums for further help.