Secure access
Configured SSH keys, non-root administration, sudo access, and authentication log review.
Administration Lab | Ubuntu Linux
Linux VPS Administration and Service Recovery
A hands-on environment for administering Ubuntu servers, supporting web services, diagnosing failures, and confirming that changes survive a restart.
Project overview
A server should be understandable before it becomes urgent.
I built the lab around common administration work: secure remote access, user and permission management, package updates, service configuration, log review, network checks, firewall rules, monitoring, and recovery. Each task ends with a verification step and a short operating note.
Administration scope
Support the whole path, not only the running process.
A web service can fail because of configuration, permissions, DNS, a blocked port, exhausted storage, or a dependency that did not start. The lab connects those layers so a failure can be investigated methodically instead of restarting services and hoping for the best.
Operating workflow
A repeatable administration cycle.
Every change moves through the same sequence: inspect, change, test, monitor, recover, and document.
Inspect
Configure
Validate
Monitor
Recover
Document
What I administered
Linux operations across the stack.
Identity and permissions
Managed users, groups, ownership, file modes, service accounts, and least-privilege access.
Services
Installed and configured Nginx and Apache, managed systemd units, and tested startup after reboot.
Network checks
Verified DNS, routes, listening ports, HTTP responses, firewall rules, and remote connectivity.
Health and capacity
Checked processes, CPU, memory, storage, package state, uptime, and scheduled jobs.
Logs and recovery
Used journal and application logs to isolate failures, roll back changes, and confirm recovery.
Command-line toolkit
Evidence before action.
I use service status, logs, ports, resource checks, and direct requests to understand the current state before changing configuration.
Validation
How I know the service is actually healthy.
Service state confirms the expected unit is active and enabled.
Listening ports confirm the process is bound to the intended interface.
DNS and HTTP checks confirm the request reaches the service and returns the expected response.
Firewall review confirms only required access is exposed.
Log review confirms there are no hidden startup or permission errors.
Restart testing confirms configuration and services persist after reboot.
Administration principles
What the lab demonstrates.
Start with the current state
Logs, service status, ports, and resource use narrow the problem before a change is made.
Change one layer at a time
Small, controlled changes make rollback easier and keep the cause visible.
Verify from the user side
A running process is not enough. DNS, connectivity, response, and restart checks complete the test.
Contact
Looking for support that understands the stack?
I’m open to technical support, customer success, SaaS support, and application support roles, remote or hybrid.