Skip to content

lab3 and 5 readme files #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 5, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions labs/lab3/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -167,7 +167,7 @@ Another nice feature of the NGINX One Console is the ability to quickly see the

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.

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.
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.

![Certs](media/lab3_oss1-certs.png)

Expand All @@ -181,24 +181,25 @@ Another nice feature of the NGINX One Console is the ability to quickly see the

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.

1. Change your Terminal to the appropriate directory, in this exercise, that would be `labs/lab2/nginx-oss/etc/ssl/nginx`.

1. Create a new `$NAME-91-day` SSL certificate/key pair:

(**NOTE:** Make sure you are within `labs/lab2` folder before running the command)

```bash
openssl req -x509 -nodes -days 91 -newkey rsa:2048 -keyout $NAME-91-day.key -out $NAME-91-day.crt -subj "/CN=NginxOneWorkshop"
openssl req -x509 -nodes -days 91 -newkey rsa:2048 -keyout nginx-oss/etc/ssl/nginx/$NAME-91-day.key -out nginx-oss/etc/ssl/nginx/$NAME-91-day.crt -subj "/CN=NginxOneWorkshop"

```

1. Verify the .crt and .key files were created, in the correct volume mounted folder:

```bash
ls -l
ls -l nginx-oss/etc/ssl/nginx

```

```bash
## Sample output ##
ubuntu@NGINX-Basics:~/Documents/nginx-one-workshops/labs/lab2/nginx-oss/etc/ssl/nginx$ ls -l
ubuntu@NGINX-Basics:~/Documents/nginx-one-workshops/labs/lab2$ ls -l nginx-oss/etc/ssl/nginx
total 32
-rw-rw-r-- 1 ubuntu ubuntu 1131 Mar 19 22:07 1-day.crt
-rw------- 1 ubuntu ubuntu 1704 Mar 19 22:07 1-day.key
Expand Down
2 changes: 1 addition & 1 deletion labs/lab5/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ Don't forget to remove your unused instances from the NGINX One Console.

## Confirm you have an R32 Instance

You will now start the process of upgrading a standalone web server. Confirm taht you have this instance by issuing the following commands:
You will now start the process of upgrading a standalone web server. Confirm that you have this instance by issuing the following commands:

1. SSH to the web server:
```bash
Expand Down