> For the complete documentation index, see [llms.txt](https://docs.n2ws.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n2ws.com/user-guide/appendix-g-securing-default-certificates-on-n2w-server.md). # Appendix G - Securing Default Certificates on N2W Server {% hint style="warning" %} *None* of the following procedures should be attempted when Backups/DR/Cleaning/S3 Copy are running. Linux Knowledge is required. {% endhint %} The N2W 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 *N2W 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 N2W 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 N2W 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: {% hint style="warning" %} Only perform these steps if you know how to use SSH and Linux commands. {% endhint %} 1. Connect to the N2W 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: --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.n2ws.com/user-guide/appendix-g-securing-default-certificates-on-n2w-server.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.