The systems layer
Linux Server & Infrastructure
Linux server setup, administration, troubleshooting, and recovery for teams that need the machine underneath the website to be dependable.
Best suited to
- Businesses inheriting an undocumented Linux server
- Teams that need a bare-metal machine configured correctly
- Sites recovering from a failed service or lost access
01 / The approach
Websites are usually discussed at the browser layer, but the operational layer is where many failures begin: a full disk, an expired certificate, a broken firewall rule, a service that will not restart, or a boot process that never reaches the login prompt.
I work with Debian/Ubuntu and RHEL-family systems, from fresh server setup to diagnosing production problems and recovering access to a failed machine. The emphasis is on careful evidence gathering, reversible changes, and documentation rather than applying commands until something happens to work.
Delivery
Based in Mymensingh, Bangladesh. Remote collaboration available for projects throughout the country and internationally.
Call +880130277623402 / What can be included
A scope shaped around the actual requirement.
Not every item below is necessary for every engagement. The right scope is agreed before implementation, not assumed from a template.
- 01Linux server provisioning and baseline hardening
- 02Bare-metal installation and configuration
- 03Web server, database, DNS, and service setup
- 04Firewall, user, SSH, and access review
- 05Boot, storage, networking, and service troubleshooting
- 06Rescue and recovery support for failed systems
- 07Backup, update, and maintenance planning
03 / Process
Establish access and evidence
The current state is recorded before changes are made. Logs, disk usage, services, network state, and recent changes provide the starting point.
Protect what still works
Backups, console access, and recovery paths are considered before risky maintenance. A fix that removes the ability to recover is not a fix.
Diagnose the actual failure
Symptoms are separated from causes. Assumptions are tested with the least disruptive command that can confirm or reject them.
Restore, document, and prevent
Service is restored, the cause is explained, and the configuration or monitoring gap that allowed the failure is addressed.
Tools & technologies
- Debian
- Ubuntu
- AlmaLinux
- CentOS
- RHEL
- nginx
- Apache
- Bash
- SSH
04 / Questions
Straight answers.
Do you work on production servers?
Yes, with a clear scope, current backup status, and an agreed maintenance window where possible. Destructive commands are not used as a shortcut without understanding the recovery path.
Can you recover a server that will not boot?
Often, but the outcome depends on the failure, available console access, storage health, and backups. A rescue attempt starts with diagnosis and the least invasive recovery option.
Which Linux distributions do you support?
Practical experience spans Debian, Ubuntu, AlmaLinux, CentOS, RHEL, and compatible distributions. The right choice depends on support requirements, team familiarity, and application constraints.
Related work
