How to add SSL certificate to Update Service Server

1. Configure SSL Certificate in IIS

  • Obtain SSL Certificate: Ensure you have a valid SSL certificate for your domain
  • Bind Certificate to IIS:
    • Open IIS Manager
    • Select your Update Service website
    • Click "Bindings" in the Actions panel
    • Add new binding for HTTPS on port 443 (or your preferred port)
    • Select your SSL certificate from the dropdown

2. Update Server Configuration

  • Configure Public URL Setting:

    • Navigate to Settings on the server interface
      • Or navigate to the appsettings.json file location
        • C:\inetpub\wwwroot\Update Service Server\appsettings.json
    • Update the PublicUrl setting to use HTTPS protocol
    • Default HTTPS (port 443): https://yourserver.example.com
    • Custom port: https://yourserver.example.com:8060
    {
    "settings": {
        "PublicUrl": "https://yourserver.example.com"
    }
}

3. Handle Existing Client Updates

Choose one of the following approaches:

Option A: Automatic Redirect (Recommended)

  • Navigate to the appsettings.json file location

  • Configure the RedirectUrl setting in appsettings.json to automatically redirect existing clients:

    {
    "settings": {
        "PublicUrl": "https://yourserver.example.com",
        "RedirectUrl": "https://yourserver.example.com"
    }
}

  • Clients will automatically update their server URL when they next connect

Option B: Manual Client Updates

  • On each client machine:
    • Open the Update Service client application
    • Navigate to the "Servers" view
    • Edit the server URL to use the new HTTPS address
    • Save the changes

4. Post-Implementation Tasks

  • Regenerate Installers: Download new installer files from the server to ensure they contain the updated HTTPS URL
  • Test Connectivity: Verify that clients can successfully connect using the new SSL-enabled URL
  • Update Documentation: Inform users about the new server URL if manual updates are required

Important Notes

  • The default HTTPS port is 443. If using a different port, it must be specified in the URL
  • Existing installers will contain the old HTTP URL and must be re-downloaded
  • Network firewalls may need to be updated to allow traffic on the new HTTPS port
  • Consider keeping the redirect setting temporarily to ensure all clients transition smoothly