Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Storage Manager (STM) > Web Console SSL changes are not saved when upgrading Storage Manager

Web Console SSL changes are not saved when upgrading Storage Manager

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1 Votes: 0 Revisions: 9

Issue

Customers who initially have their Storage Manager Web console set up for SSL access (default port 443) lose their configuration changes when upgrading Storage Manager. 
The Storage Manger web console will reset to the default port of HTTP 9000 after upgrading. 

This issue only affects customers running Linux and the following versions of Storage Manager:

  • 5.3.3
  • 5.6.2
  • 5.7.1
  • 5.7.2
  • 6.0

Resolution

After the upgrade has completed, perform the following steps to rebuild your SSL settings:

1- Navigate to the "<Storage Manager Server Installed Directory>/history/config-yyyyddmm/conf" directory and open the "server.xml" file using a text editor.

2- Copy the tag which looks like the following:

<Connector port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" URIEncoding="UTF-8" disableUploadTimeout="true" connectionTimeout="20000" acceptCount="100" redirectPort="443"  enableLookups="false" maxSpareThreads="75" minSpareThreads="25" keystoreFile="xxxxx/.keystore" keystorePass="solarwinds" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" maxHttpHeaderSize="8192"           ciphers="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,          TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,          SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA"/>

3- Navigate to the "<Storage Manager Server Installed Directory>/conf" directory and open the "server.xml" file using a text editor

4- Remove the tag which looks like the following:

<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" URIEncoding="UTF-8" disableUploadTimeout="true" connectionTimeout="20000" acceptCount="100" redirectPort="8443" enableLookups="false" maxSpareThreads="75" minSpareThreads="25" keystoreFile="webapps/ROOT/bin/.keystore"           keystorePass="solarwinds" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" maxHttpHeaderSize="8192"  ciphers="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,          TLS_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,          SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA"/>

5- Copy the tag from the "<Storage Manager Server Installed Directory>/history/config-yyyyddmm/conf/server.xml." location as in step 2 of this KB and paste it in the 
<service> tag within the "server.xml" file located in the "<Storage Manager Server Installed Directory>/conf/" directory.

6- Save the changes to the "server.xml" file in the "<Storage Manager Server Installed Directory>/conf/" location.

7- Make sure the location of your .keystore file is valid as referenced in "server.xml" file located in the "<Storage Manager Server Installed Directory>/conf/" directory 
and also make sure the .keystore file exists in it's respective location. By default this file will be removed during an upgrade if it is located in the install directory 
for Storage Manager and it is important to verify this file is present after upgrading. When the file is initially created it is stored in the home directory of the user 
creating the file.

8- Restart the SolarWinds Storage Manager Web service.

 

 

Last modified
03:49, 23 Jun 2016

Tags

Classifications

Public