Lab catalog
found 53 of 7753 of 77loading…
Loading…
-
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
-
The service can do anything The helpdesk ticket service runs as root without a single restriction — that has to change before the security review. Restrict it with systemd so that it keeps taking and storing tickets.Server security ~25 min not started
-
The service is denied access The knowledge base moved to a new disk, and the service no longer sees the articles — even though the permissions are fine and the service user reads them directly. Find what denies the access and give it back to the service without weakening its protection.Server security ~20 min not started
-
The config changes by itself The portal settings keep reverting to someone else's, even though they were just fixed. Put an audit rule on the file, find from the events who rewrites it and with what, and stop it without touching anyone else.Server security ~20 min not started
-
Container won't start A status page in a Docker container stopped opening after an edit. Find the cause and fix it.Containers: Docker and compose ~20 min not started
-
A service from a container The new version of the status page arrived as a Docker image. Run it in a container in place of the old service so that the page survives a docker restart and a machine reboot.Containers: Docker and compose ~20 min not started
-
A new image version The build of version 1.1 of the application fails. Build the app:1.1 image from the project directory and replace the running version 1.0 with it.Containers: Docker and compose ~20 min not started
-
Data after re-creation After the notes application was updated, the list is empty although the container is running. Find the notes and give them back to the application without losing any.Containers: Docker and compose ~20 min not started
-
A container restarts under load The import service moved into a container and has not processed a single export since — the container is up one moment and restarting the next. Find the cause and fix it so that the service handles the load within the limits it was given.Containers: Docker and compose ~25 min not started
-
The pricing service is down After a night-time restart the pricing service does not start. Its settings live under git, and several people have edited them. Bring back the working settings without losing yesterday's needed change and without rewriting the history.Automation: Git and Ansible ~20 min not started
-
The server does not pick up changes The developers pushed a change to the repository, but the server did not pick it up. Someone edited the settings by hand on the server last night, and that change is needed too. Update the working copy, keep both changes and push yours to the repository.Automation: Git and Ansible ~20 min not started
-
An unfinished playbook The shop status page is to be set up with an Ansible playbook instead of by hand. The playbook is started, but it fails and does not do everything. Finish it so that it sets the machine up by itself and a second run changes nothing.Automation: Git and Ansible ~25 min not started
-
First day on the server Sort out what the previous admin left behind: find the log, put the configs in place, count the failed deploys and get the tool back on the PATH.— ~30 min not started
No lab on the topic you need? Suggest a lab