HTTPS for web server in Raspberry Pi - Mini Project: Build & Apply

HTTPS for Web Server on Raspberry Pi

📖 Scenario: You want to make your Raspberry Pi web server secure by using HTTPS. HTTPS encrypts the data between your server and visitors, keeping information safe.In this project, you will create a simple web server configuration that uses HTTPS with a self-signed certificate.

🎯 Goal: Set up a basic HTTPS web server on your Raspberry Pi using Python's http.server module and SSL.You will create the certificate files, configure the server to use HTTPS, and run it.

📋 What You'll Learn

Create a self-signed SSL certificate and key files

Write Python code to start an HTTPS server using these files

Use the ssl module to wrap the server socket

Run the server on port 4443

Print a message when the server starts

💡 Why This Matters

🌍 Real World

Securing web servers on Raspberry Pi devices is important for protecting data and privacy when hosting websites or IoT dashboards.

💼 Career

Understanding HTTPS setup is useful for roles in system administration, IoT development, and web server management.

1

Create SSL certificate and key file names

Create two variables: cert_file with value "server.pem" and key_file with value "server.key" to hold the SSL certificate and key file names.

Raspberry Pi

# Create variables for SSL certificate and key file names
# Your code here

Hint

Use simple string variables to store the file names exactly as shown.

2

Import modules and create HTTP server

Import the http.server and ssl modules. Then create a variable httpd that is an HTTPServer listening on ('', 4443) with http.server.SimpleHTTPRequestHandler as the handler.

Raspberry Pi

cert_file = "server.pem"
key_file = "server.key"
# Import http.server and ssl modules
# Create HTTPServer on port 4443 with SimpleHTTPRequestHandler
# Your code here

Hint

Use http.server.HTTPServer with address ('', 4443) and handler http.server.SimpleHTTPRequestHandler.

3

Wrap server socket with SSL

Use ssl.wrap_socket to wrap httpd.socket with server_side=True, certfile=cert_file, and keyfile=key_file. Assign the result back to httpd.socket.

Raspberry Pi

cert_file = "server.pem"
key_file = "server.key"
import http.server
import ssl

httpd = http.server.HTTPServer(('', 4443), http.server.SimpleHTTPRequestHandler)
# Wrap httpd.socket with ssl.wrap_socket using cert_file and key_file
# Your code here

Hint

Use ssl.wrap_socket with the correct parameters and assign it back to httpd.socket.

4

Start HTTPS server and print message

Print "Serving HTTPS on port 4443..." and then call httpd.serve_forever() to start the server.

Raspberry Pi

cert_file = "server.pem"
key_file = "server.key"
import http.server
import ssl

httpd = http.server.HTTPServer(('', 4443), http.server.SimpleHTTPRequestHandler)
httpd.socket = ssl.wrap_socket(httpd.socket, server_side=True, certfile=cert_file, keyfile=key_file)
# Print message and start server
# Your code here

Hint

Use print to show the message, then call serve_forever() on httpd.

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