Practise this module for free on a real VM
Sign up for freeFix the server
Debug challenges: you get a broken server and no instructions. Find the cause and fix it – just like in real operations.
Debug challenge: nginx won't start
Debug challenge: nginx won't start
This lesson is different: you get no instructions, just a broken server. Find out what is wrong and fix it. Try it yourself first – after the first "Check" you get hints in three steps.
The fault is built into your VM when the lesson starts. So start the lesson right here, not from another lesson.
Exercises
1. Bring the Lab shop back online
Goal: the Lab shop is reachable again at
http://localhost/and nginx is running – with the repaired shop configuration (not deleted or replaced by another one).There are no commands up front. Investigate the server yourself.
Debug challenge: HTTPS does not answer
Debug challenge: HTTPS does not answer
This lesson is different: you get no instructions, just a broken server. Find out what is wrong and fix it. Try it yourself first – after the first "Check" you get hints in three steps.
The fault is built into your VM when the lesson starts. So start the lesson right here, not from another lesson.
Exercises
1. The shop answers over HTTPS again
Goal (1/2): on the server itself,
https://localhost/answers with the Lab shop again.Find out which port nginx really listens on for HTTPS and fix it in the configuration – no commands up front.
2. The firewall lets HTTPS through
Goal (2/2): the firewall stays active and lets HTTPS (port 443) in. SSH must stay allowed.
Debug challenge: the backdoor in cron
Debug challenge: the backdoor in cron
This lesson is different: you get no instructions, just a broken server. Find out what is wrong and fix it. Try it yourself first – after the first "Check" you get hints in three steps.
The fault is built into your VM when the lesson starts. So start the lesson right here, not from another lesson.
Exercises
1. Find and remove the backdoor
Goal (1/2): the rule that starts something every minute and the program it starts are removed from the server. The
cronservice itself keeps running.Don't worry: the "malware" is defused in the Lab and makes no real connection.
2. Make sure it does not come back
Goal (2/2): the second mechanism that would recreate the backdoor is stopped and does not start again after a reboot either. The cron rule stays gone.
Related courses
Now practice it yourself
Reading is good – doing is better. Practise this module on a real Linux VM, right in your browser. A free account is all it takes.
Start for freeLab content under CC BY 4.0 – free to use with attribution (© TechLogia).
