HTTPS for web server in Raspberry Pi - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does HTTPS stand for and why is it important for a web server?

HTTPS stands for HyperText Transfer Protocol Secure. It encrypts data between the web server and the user's browser, keeping information safe from eavesdroppers.

beginner

What is an SSL/TLS certificate in the context of HTTPS?

An SSL/TLS certificate is a digital file that proves a website's identity and enables encrypted connections. It helps browsers trust the web server and secure data transfer.

beginner

Name a common tool to create a free SSL certificate for a Raspberry Pi web server.

Let's Encrypt is a popular free tool that provides SSL certificates easily for Raspberry Pi web servers.

intermediate

What is the role of the private key in HTTPS setup?

The private key stays secret on the server and is used to decrypt data sent by users and to prove the server's identity during the HTTPS handshake.

intermediate

Why should you redirect HTTP traffic to HTTPS on your Raspberry Pi web server?

Redirecting HTTP to HTTPS ensures all user data is encrypted and secure, preventing accidental unprotected connections.

What does HTTPS protect when you visit a website?

A The server's hardware

B The website's design

C The user's computer files

D Data sent between your browser and the server

HTTPS encrypts the data sent between your browser and the web server to keep it private.

Which of these is needed to enable HTTPS on a Raspberry Pi web server?

A A faster CPU

B More RAM

C SSL/TLS certificate

D A new operating system

An SSL/TLS certificate is required to set up HTTPS and encrypt connections.

Let's Encrypt provides what kind of service?

A Paid web hosting

B Free SSL certificates

C Hardware upgrades

D Operating system updates

Let's Encrypt offers free SSL certificates to secure websites.

What should you do to make sure all visitors use HTTPS on your site?

A Redirect HTTP to HTTPS

B Disable HTTPS

C Use HTTP only

D Change the website theme

Redirecting HTTP to HTTPS forces all visitors to use the secure connection.

Where is the private key stored in HTTPS setup?

A On the web server only

B On the user's browser

C On a public website

D In the cloud only

The private key is kept secret on the web server to decrypt data and prove identity.

Explain how HTTPS secures a Raspberry Pi web server and why it matters.

Think about how data travels safely and how certificates prove identity.

Describe the steps to set up HTTPS on a Raspberry Pi web server using Let's Encrypt.

Focus on the tools and commands used to get and apply the certificate.

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