You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: labs/lab3/readme.md
+7-6Lines changed: 7 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -167,7 +167,7 @@ Another nice feature of the NGINX One Console is the ability to quickly see the
167
167
168
168
1. Using the Overview Dashboard Certificates Panel, Click on the `Expiring` link. This will provide a List View of the Instances affected, with metadata about the Instances using the Certificate.
169
169
170
-
1. Click on the `$NAME-oss1` Instance. This will provide the Instance level Details, you will see a `Certificates` Section, this time with the Name, Status, Expiration Date, and Subject Name for each certificate file.
170
+
1. Click on the `$NAME-oss1` Instance. This will provide the Instance level Details. You will see a `Certificates` Section, switch to `Unmanaged` tab. This will list the Name, Status, Expiration Date, and Subject Name for each certificate file associated to `$NAME-oss1` Instance.
171
171
172
172

173
173
@@ -181,24 +181,25 @@ Another nice feature of the NGINX One Console is the ability to quickly see the
181
181
182
182
Fix the Expired Certificate! If you want to create a new certificate, say with a 91-day expiration, follow these instructions to use `openssl` to create a Self-Signed certificate/key pair, and update your NGINX config files to use the new Certficate.
183
183
184
-
1. Change your Terminal to the appropriate directory, in this exercise, that would be `labs/lab2/nginx-oss/etc/ssl/nginx`.
185
-
186
184
1. Create a new `$NAME-91-day` SSL certificate/key pair:
187
185
186
+
(**NOTE:** Make sure you are within `labs/lab2` folder before running the command)
0 commit comments