Objective 

Prerequisites 

• Ensure you have administrative access to EventLog Analyzer and a valid SSL certificate (e.g., CRT, CER, DER, P12, PEM, P7B, JKS, or PFX) and private key (KEY). If you would like to generate and apply a self-signed certificate from EventLog Analyzer.
• Optionally, a certificate chain file (CA-BUNDLE) might be required.

Steps to follow 

• Upload the certificate file (a CRT or appropriate file).
• Upload the private key file (KEY) if required.
• Optionally upload the intermediate certificate bundle (if needed).
• If your certificate is password-protected, please enter the password in the Certificate Password field.
  

Step 5: Restart the EventLog Analyzer service for the HTTPS configuration to take effect.

Tips

• Self-signed certificates:

• Can be used for testing or internal environments.
• Must be manually trusted or browsers will display a warning.

• Internal-CA-signed certificates:

• Are ideal for enterprise environments with an internal public key infrastructure.
• Require an internal certificate authority (CA) to be trusted by client systems.

• Public-CA-signed certificates:

• Are recommended for production.
• Are trusted by all major browsers automatically.

• Ensure the HTTPS port (8445 by default) is open on your firewall.
• Back up the existing SSL certificate and key before replacing them.
• Check certificates' expiration dates and set reminders for renewal.

Related topics and articles 

• Connection settings: Help documentation
• Security hardening guide