Page Comparison

...

4. Restart your Admin Tools 2.0 service

   1. Then, load https://localhost:9181 or https://yourwebdomain:9181

Finalizing Configuration for PFX Certificate Configuration

• In web.config file, Adjusted line 33 to set https for secure connection:

// On line 33 of web.config...
<action type="Rewrite" url="https://localhost:9181/{R:1}" />

• Under nodeconfig.json, set the value for certificate and key property in certs to null or empty:

  "certs": {
    "certificate": "", <-- Follow example here 
    "key": "",         <-- Follow example here 
    "pfx": "<pfx filepath>/cert.pfx"
  },

...

Option 2: Using a key and pem file

...

5. Restart the Admin Tools server, and open the browser using the HTTPS location.

Finalizing Configuration for your HTTPS Certificate (for All Options Above)

• It is important to properly specify what configuration type that is being used for your Admin Tools certificate and nullify or providing empty values to other certificate properties. Improper specification of the certification type may cause complications when running Admin Tools.

• Under nodeconfig.json, specify which HTTPS certificate type you will use for your environment (under certs) and property in certs to null or empty:

  Example below: Using .pfx for your HTTPS certificate 
  
  "certs": {
    "certificate": "", <-- Empty value 
    "key": "",         <-- Empty value
    "pfx": "<pfx filepath>/cert.pfx", <-- pfx filepath example 
    "pfximport": ""    <-- Empty value
  },

• If using certificate and key, ensure that both contain filepath values while pfx and pfximport are left blank. If using pfximport, provide filename and leave the other property values blank.

• In web.config file, Adjusted line 33 to set https for secure connection:

// On line 33 of web.config...
<action type="Rewrite" url="https://localhost:9181/{R:1}" />

...

Related Articles:

📘 Configuring Backup My Org to Run as HTTPS

...