ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Unable to access Spectrum OneClick webpage with "HTTP Error 404.0 - Not Found"


Article ID: 224959


Updated On:


CA Spectrum DX NetOps


When trying to access the Spectrum WEB URL (https://<OneClick_HOST>:443//spectrum/admin/index.jsp), the Web server returns the error:

HTTP 404.0 - Not Found 

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.


Another application is running on the default ports used by Spectrum OneClick. These are:

  • 80 for HTTP on Windows, 8080 on Linux
  • 443 for HTTPS on Windows,  8443 on Linux

If any application, such as Microsoft IIS, is running on the ports, then Spectrum Tomcat service will not be able to start.

You can check to see what's running on any ports to identify the process at fault. For example, on the Windows command line, you can run the following to find out the Process ID of the application running on port 80:

netstat -aon | findstr 80

On Linux, it would be:

netstat -apn | grep 80

This should output something similar to:

TCP               LISTENING       1656

TCP    [::]:80              [::]:0                 LISTENING       1656


DX NetOps Spectrum all releases


If the problem is that another application, such as Microsoft IIS, is taking the HTTPS 443 port or the HTTP 80/8080 ports, then this application should be stopped as we do not recommend running other applications (such as another Web server) on any Spectrum server. 

However, you can change the HTTP/HTTPS ports Spectrum Tomcat runs on, as per:

  1. Stop the Spectrum Tomcat service if it is running.

  2. Open the server.xml for editing:


  3. Find the following section:

    <!-- Define a SSL Coyote HTTP/1.1 Connector on port 443 -->
    <Connector port="443" enableLookups="true" disableUploadTimeout="true" tcpNoDelay="true" acceptCount="100" scheme="https" secure="true" SSLEnabled="true" clientAuth="false" sslProtocol="TLS" sslEnabledProtocols="TLSv1.2" ciphers="TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256" keystoreFile="<SPECROOT>/custom/keystore/cacerts" keystorePass="changeit">
    </Connector> <!-- Define the top level container in our container hierarchy -->

    Ensure that scheme is https and then change the port to something else that is free.

  4. Repeat the same for the HTTP section.

  5. Restart the Spectrum Tomcat Web service.

  6. Repeat the above for the Spectrum WebApp:


NOTE: If you change the port to non-default, then you will have to update the URL for each user's browser that needs to access the OneClick system to reflect the new port.