Use Linux commands to inspect NGINX processes, configuration, and logs in a simple troubleshooting workflow that mirrors real operational work.
Build confidence with practical Linux troubleshooting by checking services, configs, logs, and command-line output.
Check whether NGINX is running and identify the active processes.
Check running processes with ps
Check service state
Identify the master and worker processes
Read the config and log files to understand runtime behavior.
Locate NGINX config files
Inspect config files
Read access and error logs
Search for values with grep
Summarize the issue and explain which commands were used and why.
Document what was checked
Explain what the logs show
Restart or reload if validation is needed
Check running processes with ps.
Inspect NGINX config files.
Read access and error logs.
Search config values with grep.
Validate changes and restart service if needed.
ps output shows NGINX processes
Config path is identified correctly
Access and error logs can be read
grep returns expected configuration matches
NGINX reload or restart succeeds if performed
Command notes
Troubleshooting flow summary
README with what was checked and why
Strong beginner project because it demonstrates practical troubleshooting and command-line reasoning, not just theory.
Checking the wrong log file
Ignoring permissions when reading config or logs
Restarting the service before understanding the issue
Using grep without enough context
Not distinguishing between access logs and error logs
Add journalctl-based troubleshooting
Debug reverse proxy behavior
Investigate TLS or certificate problems
Turn the workflow into a structured lab