Environment: Upgrading from and existing Avalanche v6.0 with SSL added and working, to Avalanche v6.1 THIS DOES NOT WORK WITH 6.2
Problem: After the install they are not able to connect to the Avalanche Server using "https".
Cause: The server.xml that was originally modified is overwritten with the new install.
Solution/Workaround: Setup the SSL in Tomcat again. Here are the steps.
Configuring Tomcat to Use an SSL Certificate
Once you have a PKCS #12 certificate, you can configure the Avalanche web server, Tomcat, to use encrypt traffic between the Console and the Avalanche server. This requires modifying the server.xml file and then restarting the Tomcat server.
To activate SSL for Tomcat:
1 Navigate to
[Avalanche installation directory]\Wavelink\Avalanche\apache-tomcat-7.0.35\conf
and open the server.xml file with a text editor such as Notepad.
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" />
3 Remove the comment markers <!-- and --> so that the section is not commented out.
4 Replace the section to contain the following information:
<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false"sslProtocol="TLS" keystoreFile="C:/Program Files/Wavelink/certificate.p12" keystorePass="password" keystoreType="PKCS12" />
Where the keystoreFile value is the path to the certificate and the keystorePass value is the password you entered when creating the certificate. In the path to the certificate, use forward slashes.
5 Save your changes to the file.
6 Restart the Tomcat service.
Once you have generated a certificate, activated SSL for Tomcat, and restarted the Tomcat server, you can access the Web Console over an HTTPS connection.
To access the Web Console over a secure connection:
•In the address field of your browser, type:
https://[DNS name or IP address of Avalanche]:8443/AvalancheWeb