LogoLogo
  • 1 Introduction to N2WS
  • 2 Installing and Upgrading N2WS
  • 3 Start Using N2WS
  • 4 Defining Backup Policies
  • 5 Consistent Backup with N2WS
  • 6 Windows Instances Backup
  • 7 Linux/Unix Instances Backup
  • 8 Using Elastic File System (EFS)
  • 9 Additional Backup Topics
  • 10 Performing Recovery
  • 11 Disaster Recovery
  • 12 Cross-Account DR, Backup, and Recovery
  • 13 File-Level Recovery
  • 14 Tag-based Backup Management
  • 15 Resource Control
  • 16 Security Concerns and Best Practices
  • 17 Alerts, Announcements, Notifications, and Reporting
  • 18 N2WS User Management
  • 19 N2WS IdP Integration
  • 20 Configuring N2WS with CloudFormation
  • 21 Managing Snapshots with Lifecycle Policies
  • 22 Configuring Workers
  • 23 Capturing and Cloning in Network Environments
  • 24 Orchestrating Recovery Scenarios
  • 25 Monitoring Costs and Savings
  • 26 Using N2WS with Azure
  • 27 Using Wasabi Storage
  • Appendix A -Recommended Configuration for Copy to S3
  • Appendix B - Agents Configuration Format
  • Appendix C - Time Zones
  • Appendix D - Datadog Integration
  • Appendix E - Splunk Integration Support
  • Appendix F - Resetting Root Password or MFA
  • Appendix G - Securing Default Certificates on N2WS Server
Powered by GitBook
On this page

Was this helpful?

Export as PDF

Appendix G - Securing Default Certificates on N2WS Server

PreviousAppendix F - Resetting Root Password or MFA

Was this helpful?

None of the following procedures should be attempted when Backups/DR/Cleaning/S3 Copy are running. Linux Knowledge is required.

The N2WS server comes with a default self-signed HTTPS certificate that will show as ‘Not Secure’ in the browser. You can secure the certificate and reach the UI by either:

  • Selecting the Advanced button in the ‘Your connection is not private” message, or

  • Adding an exception to the browser. See the Appendix B screenshot in the N2WS Quick Start Guide at

If you purchased an HTTPS certificate from a certificate authority, you can replace the default certificate with the new one as follows:

  1. Connect to the N2WS instance over SSH.

  2. Use ‘sudo’ to reach the certificate folder, keeping the ownership and permissions of the files (‘cp’).

  3. Go to /opt/n2wsoftware/cert

cd /opt/n2wsoftwar/cert

4. In the folder, replace cpm_server.crt and cpm_server.key with new files having the same names.

5. If you are using MobaXterm, you can drag/drop files to the SSH session, and then copy the files to the correct folder.

6. After replacing the files, restart Apache: sudo service apache2 restart

For full details, see

To test the certificate before deploying to production:

The user can launch a new N2WS trial instance to see if the new certificate works there.

If there are any issues, you can restore/recreate the original default certificate as follows:

Only perform these steps if you know how to use SSH and Linux commands.

  1. Connect to the N2WS instance over SSH using a tool such as PuTTY or MobaXterm.

  2. Use ‘sudo’ to reach the certificate folder, keeping the ownership and permissions of the files: sudo su

  3. Go to /opt/n2wsoftware/cert: 

cd /opt/n2wsoftwar/cert

4. Move the existing .crt and .key files to a new name:

mv cpm_server.crt backup_cpm_server.crt
mv cpm_server.key backup_cpm_server.key

5. Stop/Start the instance.

For full details, see

https://docs.n2ws.com/quick-start/appendix-b-adding-exception-for-default-browser
https://support.n2ws.com/portal/en/kb/articles/how-to-change-the-certificat-and-key-used-by-cpm
https://support.n2ws.com/portal/en/kb/articles/how-to-restore-recreate-the-default-server-certificate