Basic Navigation
The first areas to learn in WebAdmin are the places where most daily administration happens.
A useful mental map
WebAdmin makes more sense when you follow the same order a real request follows through the server.
That order is usually:
- traffic arrives at a listener
- the hostname maps to a virtual host
- the virtual host decides how to serve or route the request
- server-wide rules shape logging, security, and process behavior
Start here
ListenersVirtual HostsServer ConfigurationSecurityTools
What each area usually controls
| Area | What you do there |
|---|---|
Listeners | define ports, IPs, and SSL entry points |
Virtual Hosts | define per-site roots, mappings, and contexts |
Server Configuration | tune global process, logging, and connection behavior |
Security | review restrictions, TLS, and request protections |
Tools | inspect status and trigger graceful actions |
A good beginner workflow
If you are learning a new server, avoid clicking randomly. Instead, use this sequence:
- identify the listener receiving traffic
- identify the virtual host serving the domain
- confirm the document root and site-level settings
- confirm whether PHP or other handlers are attached
- check logs and tools if behavior is still unclear
Learning order
Begin with listeners and virtual hosts, then move into PHP handlers, logging, and SSL. That mirrors how traffic actually flows through the server.
Practical habit
When changing something in WebAdmin, always note which layer you changed: listener, virtual host, or server-wide setting. That habit makes troubleshooting much easier later.
Why this matters operationally
Most configuration confusion comes from changing the wrong layer. A listener problem, a virtual host problem, and a server-wide problem can look similar from the browser. Good navigation habits help you isolate the right layer faster.