- 4 minutes to read

Step 5: Remove Core Services

Remove old Nodinite v6 Core Services web applications, custom SSL/TLS websites, and conflicting hostname bindings from IIS.

Warning

Skipping this step is the leading cause of failures in Step 11: Configure TLS. Custom SSL websites from v6 and any hostname bindings on other sites must be fully removed now, or TLS configuration will fail with binding conflicts.

Prerequisites

Steps

1. Remove Old v6 Web Applications

  1. Open IIS Manager on the Nodinite Application Server

  2. Expand server node → Sites

  3. Locate the site hosting old Nodinite applications (typically Default Web Site)

  4. Remove old applications:

    • Right-click /Nodinite/ENV/WebClient → Remove
    • Right-click /Nodinite/ENV/WebAPI → Remove
    • Right-click /Nodinite/ENV/LogAPI → Remove
    • Right-click /NodiniteUpdate/UpdateClient → Remove

  5. Remove old application folders:

    • Right-click NodiniteUpdate folder → Remove
    • Right-click Nodinite folder → Remove

2. Remove Custom SSL/TLS Website

In Nodinite v6, a dedicated custom website in IIS was commonly created to terminate TLS (HTTPS) for the Nodinite services. This website is no longer needed in v7 — TLS is now configured differently in Step 11: Configure TLS.

Important

Before removing the custom website, note down:

  • The Host Name (e.g., nodinite.yourdomain.com) — you will need this in Step 11
  • The Certificate Thumbprint bound to the site — you will need this in Step 11

To remove the custom website:

  1. In IIS Manager, expand Sites
  2. Identify any site that was created specifically for Nodinite v6 TLS (e.g., named "Nodinite", "Nodinite SSL", or similar — it is not the Default Web Site)
  3. Expand the site node and remove any web applications inside it first:
    • Right-click each application under the site → Remove
  4. Right-click the site itself → Remove

3. Remove Conflicting Hostname Bindings

Even if you did not have a dedicated custom website, the hostname used for Nodinite (e.g., nodinite.yourdomain.com) may already be registered as a binding on Default Web Site or another existing site. If this hostname binding is not removed, Step 11 (Configure TLS) will fail because IIS cannot bind the same hostname to two different sites.

To check and remove conflicting bindings:

  1. In IIS Manager, click Default Web Site (and any other site present)
  2. In the Actions panel on the right, click Bindings...
  3. Look for any binding that uses the Nodinite hostname (e.g., nodinite.yourdomain.com) or its certificate thumbprint
  4. Select the conflicting binding → Remove → Close

4. Remove Old Application Pools

Remove application pools that were created for v6 and are no longer associated with any application.

IIS Application Pools showing v6-era pools to remove
Example of the IIS Application Pools list showing old Nodinite v6 pools that should be removed after the web applications have been deleted.

To identify and remove old pools:

  1. In IIS Manager, click Application Pools

  2. Look for pools with no applications (the Applications column shows 0)

  3. Look for pools with v6-era names such as Nodinite - Update Client, Nodinite DEV LogAPI, Nodinite DEV WebAPI, Nodinite DEV WebClient

  4. Right-click each old pool → Remove

  5. Go to Portal and proceed to the next step

Completion Checklist

  • Old v6 web applications removed from IIS
  • Old application folders removed from IIS
  • Custom SSL/TLS website removed (if present)
    • Host Name documented for use in Step 11
    • Certificate Thumbprint documented for use in Step 11
  • Hostname bindings removed from Default Web Site and any other sites
  • Old v6 application pools removed

Next Step

Troubleshooting

Cannot Remove Application – "In Use"

Problem: IIS shows "file in use" error.

Solution:

  • Stop the application pool first
  • Close any open browser tabs pointing to old URLs
  • Stop the IIS site temporarily
  • Try again

Step 11 Fails with Binding Conflict

Problem: TLS configuration in Step 11 fails because the hostname is already bound to another site.

Solution:

  • Return to this step and check all sites in IIS Manager for bindings using the Nodinite hostname
  • Remove every matching binding before retrying Step 11