Web Manager
Web Manager controls how each hosted domain is served and which domain-level HTTPS, request-protection, access, and redirect policies SHM should generate.
Where to find it: Open the account and choose Web Manager.
Available to: The account user for their own account, plus root or the owning reseller when working inside that account. The item may be hidden when its feature profile or required service is disabled.
What this page does
Use it to route a domain to PHP, a Node.js application, or a container-backed port where supported; enforce HTTPS; enable HTTP Guard or ModSecurity; apply access restrictions; and create redirects that preserve the intended URI and query string.
Before you start
Confirm the selected domain, active server stack, document root or application port, and a working baseline before changing routing or security. A wrong backend port can turn a healthy application into a very convincing 502.
Application routing
| Backend | Use it when | Verify |
|---|---|---|
| PHP | The domain serves files through the selected account PHP runtime. | Document root, PHP version, pool, and public response. |
| Node.js | An account-owned application listens on the configured port and is managed through Node.js Manager. | PM2/app state, listening port, logs, and public proxy response. |
| Podman / container port | An authorized account container exposes the application on a supported local port. | Container state, port mapping, logs, and public proxy response. |
Domain policy
- HTTPS redirect sends supported HTTP requests to HTTPS after a valid certificate exists.
- HTTP Guard activates the root-configured request-protection policy for this domain.
- ModSecurity applies the supported web application firewall policy.
- Access restrictions limit the domain or path using the controls shown by the current page.
- Redirects send matching paths or the full domain to a selected destination while preserving URI/query behavior described by the form.
Bulk actions
Bulk controls apply one supported policy to several selected domains. Review the selection first; domains can use different runtimes and customer requirements even when their names look related.
How to use it
- Select the exact domain and read its current routing.
- Confirm the destination runtime or redirect target is already healthy.
- Change the backend or policy and save.
- Wait for generated web configuration to apply.
- Test HTTP, HTTPS, representative paths, login/API traffic, redirects, and application logs.
Result and next check
The domain's saved web settings and generated runtime agree, and the public request reaches the intended application with the selected HTTPS and protection behavior.
Theme color