Applications Systems

DPA website is not accessible after an upgrade to 2025.2 and displays an error "ERR_CONNECTION_REFUSED"

This article explains the recent changes in the server.xml file that made the DPA web console unaccessible after upgrading to 2025.2.

First published date

6/8/2025 2:27 AM

Last published date

6/8/2025 2:27 AM

Overview

If you are upgrading from DPA 2024.4.200 or earlier to DPA 2025.2 and added or changed any of the additional properties within the server.xml file, you need to manually configure those properties. One Windows the DPA installer will create a backup of the server.xml in the format appended with date, for example: server-20250513-083327-backup.

Manually update the new server.xml file at C:\Program Files\SolarWinds\DPA\iwc\tomcat\conf\server.xml. Map the old properties to the new properties as shown in the table below.

Product section

Database Performance Analyzer

Cause

You will see errors something like these in the Catalina<date>.log. {DPA Dir}DPA\iwc\tomcat\logs

06-Jun-025 08:59:19.684 INFO [main] com.confio.ignite.keys.certificates.CertificateConfigurationTask.getHostName Host name resolved to [SubjectNames{commonName='<FQDN>', hostNames=[ServerName/HostName], ips=[IP_Address, 0:0:0:0:0:0:0:1]}]

06-Jun-2025 08:59:19.689 INFO [main] com.confio.ignite.keys.certificates.CertificateConfigurationTask.run Interrogating keystore file [D:\Program Files\SolarWinds\DPA\iwc\tomcat\conf\.keystore]

06-Jun-2025 08:59:20.034 INFO [main] com.confio.ignite.keys.certificates.CertificateConfigurationTask.run Alias name not specified.

06-Jun-2025 08:59:20.034 INFO [main] com.confio.ignite.keys.certificates.CertificateConfigurationTask.run Key entry exists in keystore.

06-Jun-2025 08:59:20.039 INFO [main] com.confio.ignite.keys.certificates.CertificateConfigurationTask.handleCertificate Certificate in keystore under alias [tomcat] is not self-signed or DN does not match the template DN. No action.

06-Jun-2025 08:59:20.084 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8123"]

06-Jun-2025 08:59:20.174 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["https-jsse-nio-8124"]

06-Jun-2025 08:59:20.724 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector["https-jsse-nio-8124"]]

org.apache.catalina.LifecycleException: Protocol handler initialization failed

at org.apache.catalina.connector.Connector.initInternal(Connector.java:1051)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:122)

at org.apache.catalina.core.StandardService.initInternal(StandardService.java:522)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:122)

at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:957)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:122)

at org.apache.catalina.startup.Catalina.load(Catalina.java:712)

at org.apache.catalina.startup.Catalina.load(Catalina.java:735)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:569)

at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:302)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:475)

Caused by: java.lang.IllegalArgumentException: Get Key failed: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.

at org.apache.tomcat.util.net.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:114)

at org.apache.tomcat.util.net.AbstractJsseEndpoint.initialiseSsl(AbstractJsseEndpoint.java:70)

at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:200)

at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1304)

at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1317)

at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:633)

at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:82)

at org.apache.catalina.connector.Connector.initInternal(Connector.java:1049)

... 13 more

Caused by: java.security.UnrecoverableKeyException: Get Key failed: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.

at java.base/sun.security.pkcs12.PKCS12KeyStore.engineGetKey(PKCS12KeyStore.java:450)

at java.base/sun.security.util.KeyStoreDelegator.engineGetKey(KeyStoreDelegator.java:91)

at java.base/java.security.KeyStore.getKey(KeyStore.java:1050)

at org.apache.tomcat.util.net.SSLUtilBase.getKeyManagers(SSLUtilBase.java:393)

at org.apache.tomcat.util.net.SSLUtilBase.createSSLContext(SSLUtilBase.java:268)

at org.apache.tomcat.util.net.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:112)

... 20 more

Caused by: javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.

at java.base/com.sun.crypto.provider.CipherCore.unpad(CipherCore.java:862)

at java.base/com.sun.crypto.provider.CipherCore.fillOutputBuffer(CipherCore.java:942)

at java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:735)

at java.base/com.sun.crypto.provider.PBES2Core.engineDoFinal(PBES2Core.java:325)

at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2205)

at java.base/sun.security.pkcs12.PKCS12KeyStore.lambda$engineGetKey$0(PKCS12KeyStore.java:371)

at java.base/sun.security.pkcs12.PKCS12KeyStore$RetryWithZero.run(PKCS12KeyStore.java:257)

at java.base/sun.security.pkcs12.PKCS12KeyStore.engineGetKey(PKCS12KeyStore.java:361)

OR this error

10-Aug-2025 04:36:01.618 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector["https-jsse-nio-8124"]]
org.apache.catalina.LifecycleException: Protocol handler initialization failed
Caused by: java.lang.IllegalArgumentException: No SSLHostConfig element was found with the hostName [_default_] to match the defaultSSLHostConfigName for the connector [https-jsse-nio-8124]

Resolution

Manually update the new server.xml file at C:\Program Files\SolarWinds\DPA\iwc\tomcat\conf\server.xml. Map the old properties to the new properties as shown in the table below.

Old Property	New Property	Formatting example
`keystoreType="PKCS12"`	`certificateKeystoreType="PKCS12"`	The updated format should look like the example below. `<SSLHostConfig hostName="dpasslhost"> <Certificate certificateKeystoreFile="conf/.keystore" certificateKeystoreType="PKCS12" type="RSA" /> </SSLHostConfig>`
`keystorePass="password"`	`certificateKeystorePassword="password"`	The updated format should look like the example below. `<SSLHostConfig hostName="dpasslhost"><Certificate certificateKeystoreFile="conf/.keystore"certificateKeystoreType="PKCS12"certificateKeyAlias="somealias"certificateKeystorePassword="password"certificateKeyPassword="keypassword"type="RSA" /></SSLHostConfig>`
`keyPass="keypassword"`	`certificateKeyPassword="keypassword"`	The updated format should look like the example below. `<SSLHostConfig hostName="dpasslhost"><Certificate certificateKeystoreFile="conf/.keystore"certificateKeystoreType="PKCS12"certificateKeyAlias="somealias"certificateKeystorePassword="password"certificateKeyPassword="keypassword"type="RSA" /></SSLHostConfig>`
`keyAlias="somealias"`	`certificateKeyAlias="somealias"`	The updated format should look like the example below. `<SSLHostConfig hostName="dpasslhost"><Certificate certificateKeystoreFile="conf/.keystore"certificateKeystoreType="PKCS12"certificateKeyAlias="somealias"certificateKeystorePassword="password"certificateKeyPassword="keypassword"type="RSA" /></SSLHostConfig>`

Full article details:

https://documentation.solarwinds.com/en/success_center/dpa/content/dpa-upgrade-dpa-on-windows.htm

For customers running DPA on Linux:

Backup server.xml before moving to Step 6 as per Upgrade DPA on a Linux-based OS
Then do step 7 (copy old confs to new etc.)
Restore new server.xml
Edit Server.xml to replace hostName="dpasslhost" and defaultSSLHostConfigName="dpasslhost" with the dpa server hostname and any other changes you made earlier in your old server.xml file
Start DPA service.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.