Lab catalog
found 9 of 779 of 77loading…
Loading…
-
Netplan: restore the link to the neighbour The training interface lab0 is up, yet the neighbour 192.0.2.1 does not answer. Find the cause and fix the persistent network configuration without touching anything else.~25 min not started
-
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.~30 min not started
-
Ports: start the app service The app web service will not start. Find out what is in its way and bring it up on its usual port, 8080.~20 min not started
-
Firewall: open the site to the office The server's site must open from the office and stay closed to everyone else, yet the office waits until the timeout. Find the cause and fix the persistent nftables configuration.~25 min not started
-
Internal names do not resolve The name app.internal does not resolve, although the DNS server runs on this very machine. Find out why the system does not ask it and fix that.~15 min not started
-
SSH key login isn't working The key for deploy is on the server, yet the login is refused. Use the log to find what the server distrusts and restore the login.~20 min not started
-
Keep only the authorized SSH access A dedicated SSH server on 127.0.0.1:2222 lets in too many. Leave key-only access for deploy, deny root and check a fresh connection.~25 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.~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.~40 min not started
No lab on the topic you need? Suggest a lab