Update invalid-cert.md

content/en/hub/additional-topics/legacy/fn-legacy-docs/invalid-cert.md

@@ -1,31 +1,28 @@
 ---
 title: "How to Recover from an Invalid Certificate"
-description: "How to Recover from an Invalid Certificate"
 ---
 
-
-
-**DESCRIPTION** 
+## DESCRIPTION
 
 After updating to 9.10, the old style of self signed certificates in 9.3 will no longer work. This is due to a minor 9.3 bug that was fixed in the 9.10 update, but can prevent access to the web GUI in some web browsers.
 
-**ISSUE**
+## ISSUE
 
-After updating to 9.10, an invalid certificate error occurs in the web browser, blocking entry to the web GUI. When a certificate is self-signed by an internal CA, it is flagged as invalid or insecure, as web browsers by default only trust certificates that are signed by external CAs like Verisign. To prevent this issue, remove all internal CAs and internal certificates before updating to 9.10. If the update was already performed, the fix is to temporarily disable HTTPS from the Shell to make the web GUI accessible.
+After updating to 9.10, an invalid certificate error occurs in the web browser, blocking entry to the web GUI. When a certificate is self-signed by an internal CA, it is flagged as invalid or insecure, as web browsers by default only trust certificates that are signed by external CAs like Verisign. To prevent this issue, remove all internal CAs and internal certificates before updating to 9.10. If the update was already performed, the fix is to temporarily disable HTTPS from the *Shell* to make the web GUI accessible.
 
-**FIX**
+## FIX
 
-To regain web GUI access to a system containing an invalid certificate, HTTPS must first be disabled from the Shell so that the invalid certificate can be removed and replaced using the web GUI. The Shell can be accessed from the Console Setup menu which appears at the end of the boot process. If the SSH service has been enabled, it can also be used.
+To regain web GUI access to a system containing an invalid certificate, HTTPS must first be disabled from the *Shell* so that the invalid certificate can be removed and replaced using the web GUI. The *Shell* can be accessed from the Console Setup menu which appears at the end of the boot process. If the SSH service has been enabled, it can also be used.
 
-1.) Once in the Shell, set the GUI protocol to HTTP by entering the following command:
+1. Once in the Shell, set the GUI protocol to *HTTP* by entering the following command:
   `sqlite3 /data/freenas-v1.db “update system_settings set stg_guiprotocol = ‘http’;”`
-This will configure the FreeNAS® system to boot without using a certificate.
+This will configure the FreeNAS system to boot without using a certificate.
 
-2.) The next step is to reboot the system. Type exit to leave the Shell, then enter 13 from the menu. Enter y to confirm reboot.
+2. The next step is to reboot the system. Enter `exit` to leave the Shell, then enter `13` from the menu. Enter `y` to confirm reboot.
 
-3.) Log in to the web GUI, ensuring http:// is at the beginning of the URL.
+3. Log in to the web GUI, ensuring `http://` is at the beginning of the URL.
 
-4.) To delete the 9.3 CA and certificates, go to:  System -> CAs.
+4. To delete the 9.3 CA and certificates, go to *System -> CAs*.
 
 <img src="/images/fn-9.1-cert-1.png">
 <br><br>
@@ -35,9 +32,9 @@ This will configure the FreeNAS® system to boot without using a certificate.
 <img src="/images/fn-9.1-cert-2.png">
 <br><br>
 
-4.2 Click Delete at the bottom of the screen to remove the internal CA and its certificates.
+4.2 Click **Delete** at the bottom of the screen to remove the internal CA and its certificates.
 
-5.) To create the new internal CA, click Create Internal CA.
+5. To create the new internal CA, click **Create Internal CA**.
 
 <img src="/images/fn-9.1-cert-3.png">
 <br><br>
@@ -47,39 +44,39 @@ This will configure the FreeNAS® system to boot without using a certificate.
 <img src="/images/fn-9.1-cert-4.png">
 <br><br>
 
-5.2 Click OK to save.
+5.2 Click **OK** to save.
 
-6.) To create the new self-signed certificate, go to System -> Certificates.
+6. To create the new self-signed certificate, go to *System -> Certificates*.
 
 <img src="/images/fn-9.1-cert-5.PNG">
 <br><br>
 
-6.1 Click Create Internal Certificate.
+6.1 Click **Create Internal Certificate**.
 
-6.2 From the configuration screen, use the Signing Certificate Authority drop-down menu to select the new internal CA.
+6.2 From the configuration screen, use the *Signing Certificate Authority* drop-down menu to select the new internal CA.
 
 <img src="/images/fn-9.1-cert-6.png">
 <br><br>
 
-6.3 Fill in the fields that apply. The domain name or hostname of the system must be used in the Common Name field. Click OK to save.
+6.3 Fill in the fields that apply. The domain name or hostname of the system must be used in the *Common Name* field. Click **OK** to save.
 
-7.) To enable HTTPS with the new certificate, go to System -> General.
+7. To enable HTTPS with the new certificate, go to *System -> General*.
 
 <img src="/images/fn-9.1-cert-7.png">
 <br><br>
 
-7.1 Select HTTPS from the Protocol drop-down menu.
+7.1 Select **HTTPS** from the *Protocol* drop-down menu.
 
 <img src="/images/fn-9.1-cert-8.png">
 <br><br>
 
-7.2 Select the new certificate from the drop-down menu. Click Save.
+7.2 Select the new certificate from the drop-down menu. Click **Save**.
 
 7.3 Refresh the web browser to ensure HTTPS is enabled.
 
-8.) To save the updated 9.10 configuration, go to System -> General.
+8. To save the updated 9.10 configuration, go to *System -> General*.
 
 <img src="/images/fn-9.1-cert-9.png">
 <br><br>
 
-8.1 Click Save Config.
+8.1 Click **Save Config**.