HTTPS for web server in Raspberry Pi - Step-by-Step Execution

Concept Flow - HTTPS for web server

Start Web Server Setup

↓

Generate SSL Certificate

↓

Configure Server for HTTPS

↓

Start Server with HTTPS

↓

Client Requests HTTPS

↓

Server Sends Encrypted Response

↓

Client Decrypts and Displays

↓

End

This flow shows how a web server on Raspberry Pi is set up to use HTTPS by generating certificates, configuring the server, and handling encrypted client requests.

Execution Sample

Raspberry Pi

openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes -subj "/CN=localhost"
python3 -c "import http.server, ssl; httpd = http.server.HTTPServer(('0.0.0.0', 4443), http.server.SimpleHTTPRequestHandler); context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER); context.load_cert_chain(certfile='cert.pem', keyfile='key.pem'); httpd.socket = context.wrap_socket(httpd.socket, server_side=True); httpd.serve_forever()"

Generate SSL certificate and start a simple HTTPS web server on Raspberry Pi.

Execution Table

Step	Action	Command/Code	Result/Output
1	Generate SSL certificate and key	openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes -subj "/CN=localhost"	Created key.pem and cert.pem files
2	Start HTTPS server with generated cert and key	python3 -c "import http.server, ssl; httpd = http.server.HTTPServer(('0.0.0.0', 4443), http.server.SimpleHTTPRequestHandler); context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER); context.load_cert_chain(certfile='cert.pem', keyfile='key.pem'); httpd.socket = context.wrap_socket(httpd.socket, server_side=True); httpd.serve_forever()"	Server listens on port 4443 with HTTPS
3	Client sends HTTPS request	Browser visits https://<raspberry_pi_ip>:4443	Server receives encrypted request
4	Server responds with encrypted data	Server sends encrypted HTML files	Client receives encrypted response
5	Client decrypts and displays page	Browser decrypts using cert	Page shown securely
6	Server runs continuously	No new commands	HTTPS server active
7	Stop server	Ctrl+C	Server stops

💡 Server stops when user interrupts (Ctrl+C) or system shuts down

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 6	Final
key.pem	Not created	Created	Used by server	Used by server	Exists
cert.pem	Not created	Created	Used by server	Used by server	Exists
Server status	Stopped	Stopped	Running	Running	Stopped

Key Moments - 3 Insights

Why do we need to generate key.pem and cert.pem before starting the server?

The server needs these files to encrypt and decrypt data for HTTPS. Without them, it cannot secure connections (see execution_table step 1 and 2).

What happens if the client tries to connect without HTTPS?

The server is configured only for HTTPS on port 4443, so plain HTTP requests will fail or be rejected (see execution_table step 3).

Why does the server keep running after starting and how do we stop it?

The server runs continuously to serve requests until manually stopped by Ctrl+C (see execution_table step 6 and 7).

Visual Quiz - 3 Questions

Look at the execution_table, what files are created at step 1?

A config.json and key.pem

B index.html and server.py

C key.pem and cert.pem

D cert.pem and index.html

💡 Hint

Check the 'Result/Output' column in step 1 of execution_table

At which step does the server start listening for HTTPS requests?

A Step 1

B Step 2

C Step 3

D Step 6

💡 Hint

Look at the 'Action' and 'Result/Output' columns in execution_table

If the server is stopped, what is the status of 'Server status' variable in variable_tracker?

A "Stopped"

B "Running"

C "Starting"

D "Error"

💡 Hint

Check the last column 'Final' for 'Server status' in variable_tracker

Concept Snapshot

HTTPS for web server on Raspberry Pi:
1. Generate SSL key and certificate files (key.pem, cert.pem).
2. Configure and start server with these files for HTTPS.
3. Server listens on secure port (e.g., 4443).
4. Client connects securely, data is encrypted.
5. Server runs until manually stopped.

Full Transcript

This visual execution shows how to set up HTTPS on a Raspberry Pi web server. First, you generate SSL certificate and key files using openssl. Then you start the Python HTTPS server with these files, listening on port 4443. When a client connects via HTTPS, the server sends encrypted data which the client decrypts to display the webpage securely. The server keeps running until stopped by the user. Variables like key.pem, cert.pem, and server status change as the steps progress. This setup ensures secure communication between client and server.

Practice

1. What is the main purpose of using HTTPS on a Raspberry Pi web server?

easy

A. To make the website load faster

B. To change the website's design automatically

C. To allow more users to connect simultaneously

D. To encrypt data and keep the website safe

Solution

1. Step 1: Understand HTTPS function

   HTTPS encrypts data between the user and the server to protect privacy and security.

2. Step 2: Compare options

   Only To encrypt data and keep the website safe correctly describes HTTPS purpose; others are unrelated to encryption.

3. Final Answer:

   To encrypt data and keep the website safe -> Option D

4. Quick Check:

   HTTPS = encrypt data [OK]

Hint: HTTPS means secure data transfer with encryption [OK]

Common Mistakes:

• Thinking HTTPS speeds up the website
• Confusing HTTPS with website design
• Believing HTTPS increases user capacity

2. Which command correctly stops the Apache web server on Raspberry Pi before obtaining an SSL certificate?

easy

A. sudo systemctl stop apache2

B. sudo start apache2

C. apache2 stop sudo

D. stop apache2 sudo

Solution

1. Step 1: Recall correct systemctl syntax

   The command to stop a service is 'sudo systemctl stop servicename'.

2. Step 2: Identify correct option

   sudo systemctl stop apache2 matches the correct syntax to stop Apache2; others are invalid commands.

3. Final Answer:

   sudo systemctl stop apache2 -> Option A

4. Quick Check:

   Stop service = sudo systemctl stop [OK]

Hint: Use 'sudo systemctl stop apache2' to stop Apache safely [OK]

Common Mistakes:

• Using incorrect command order
• Omitting 'sudo' for permissions
• Using 'start' instead of 'stop'

3. What will be the output of this command on Raspberry Pi after installing Certbot and running it to get a certificate?

sudo certbot --apache

medium

A. It automatically obtains and installs an SSL certificate for Apache

B. It deletes all Apache configuration files

C. It starts the Apache server without SSL

D. It shows an error because Certbot is not compatible

Solution

1. Step 1: Understand Certbot command

   The command 'sudo certbot --apache' requests and installs SSL certificates automatically for Apache.

2. Step 2: Evaluate options

   Only It automatically obtains and installs an SSL certificate for Apache correctly describes the expected behavior; others are incorrect or false.

3. Final Answer:

   It automatically obtains and installs an SSL certificate for Apache -> Option A

4. Quick Check:

   Certbot --apache = get SSL cert [OK]

Hint: Certbot with --apache auto installs SSL cert [OK]

Common Mistakes:

• Thinking Certbot deletes files
• Assuming Certbot starts server
• Believing Certbot is incompatible with Apache

4. You tried to get an SSL certificate but forgot to stop Apache first. What error will most likely occur?

medium

A. No internet connection error

B. Certificate installed successfully

C. Port 80 is already in use error

D. Apache configuration syntax error

Solution

1. Step 1: Understand port usage during certificate request

   Certbot needs to use port 80 to verify domain ownership, but Apache uses it if running.

2. Step 2: Identify error from port conflict

   If Apache is not stopped, Certbot cannot bind port 80, causing 'Port 80 is already in use' error.

3. Final Answer:

   Port 80 is already in use error -> Option C

4. Quick Check:

   Apache running blocks port 80 for Certbot [OK]

Hint: Stop Apache before Certbot to avoid port 80 conflict [OK]

Common Mistakes:

• Ignoring need to stop Apache
• Expecting success without stopping server
• Confusing error with internet issues

5. After successfully obtaining an SSL certificate on Raspberry Pi, what is the correct sequence to enable HTTPS on your Apache web server?

hard

A. Restart Apache, then configure firewall to allow port 443

B. Configure firewall to allow port 443, then restart Apache

C. Restart Apache only, no firewall changes needed

D. No action needed; HTTPS works automatically without restart

Solution

1. Step 1: Open firewall port 443 for HTTPS

   Before restarting Apache, ensure firewall allows HTTPS traffic on port 443.

2. Step 2: Restart Apache to apply SSL certificate

   Restarting Apache activates the new SSL certificate and enables HTTPS.

3. Final Answer:

   Configure firewall to allow port 443, then restart Apache -> Option B

4. Quick Check:

   Firewall open 443, then restart Apache [OK]

Hint: Open port 443 before restarting Apache for HTTPS [OK]

Common Mistakes:

• Restarting Apache before opening firewall port
• Assuming no firewall changes needed
• Believing HTTPS works without restart