Lab catalog
found 9 of 779 of 77loading…
Loading…
-
A service behind the neighbour The reports service on node2 answers itself, but a request from node1 waits and gives up. Find where the path gets lost and fix it so that the fix survives a reboot.Networking ~30 min not started
-
Connect two VMs over the network The site works on node2, but a request from node1 waits and gives up. Find on which machine and at which stage it gets lost, and restore access.Networking ~30 min not started
-
Site unreachable from another host The site on node2 answers itself but does not open from node1. There may be several causes — find them all and keep nginx healthy.Networking ~40 min not started
-
The clocks of two machines drift apart The reports from the node1 server are two hours ahead, and the events in the logs of node1 and node2 do not line up. The office time comes from node2. Make the node1 clock follow node2 — now and after the time service restarts.Inside the system: resources, kernel, processes ~25 min not started
-
Too much is visible from the network The warehouse server runs a site, a database and an admin panel, and only the site and SSH should be visible from the network. Find what else is open to the outside and close it so that everything still works on the server itself, after a reboot too.Server security ~35 min not started
-
The brute force goes on Someone on the neighbouring machine keeps trying to log in to the server's SSH. fail2ban is installed and running, a colleague has even tuned it, and still there is no ban. Find out why and make sure the attacker gets banned and the administrator never does.Server security ~30 min not started
-
A site and its database on two machines The orders site moved to node1 while its database stayed on node2, and the site stopped opening. Find every cause and leave the database open to the site only.— ~50 min not started
-
A server ready for publication A new ticket server is about to go public, but the security review sent it back. Leave key-only login without root, close the extra ports, turn on brute-force protection and confine the service — so that all of it holds after a reboot.— ~60 min not started
-
A site on node2, by a playbook from node1 A colleague's playbook is meant to bring up a status page on node2 from node1, yet it finishes without errors and there is no page. Fix the project so that the playbook configures node2 and a second run changes nothing.— ~50 min not started
No lab on the topic you need? Suggest a lab