> For the complete documentation index, see [llms.txt](https://docs.n2ws.com/quick-start/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/quick-start/appendix-b-adding-exception-for-default-browser.md).

# Appendix B  - Adding Exception for Default Browser for N2W

### For Chrome

When you first navigate to your N2W instance, you'll see a screen like this. It's nothing to worry about. We are SSL secured but because it is a self-signed certificate, you may want to add an exception to your browser following these steps.

![](/files/-MZddKDiq0Z_dM7UMxKK)

1. Open the Chrome browser. In the top right, select **More** ![](/files/-M9KiWCcqRFJQAiWRsnk).
2. Select **Settings**, **Advanced**, and then in the **System** section, select **Open** **proxy settings.**

![](/files/-MZddR4OKCxCD5DLPvDk)

&#x20;   3\. Choose the **Security** tab and then select **Trusted Sites**.

![](/files/-MZddYOpolGcjVAiQabY)

&#x20;   4\. Select the **Sites** button.

&#x20;   5\. Type the N2W server’s IP address in the **Add this website to the zone** box, and then select **Add**, **Close**. and **OK**.

![](/files/-MZdddcCbhvY2Tz5zhH8)

You should not get the warning on the certificate again.

### For Firefox

The example is from Firefox Quantum.&#x20;

1. Select **Advanced,** the "1" label in the screenshot below.&#x20;
2. Select **Add Exception** for this server, the "2" label in the screenshot below.

![](/files/-MZddlj7Qwr8QA3faF5y)
