Server settings & services

Requires WHP super admin access. These features are unlocked for customers with a WHP super admin role on the server — for example, anyone running a Virtual Dedicated Server. Customers without super admin won’t see these pages.

Draft — work in progress

This page is a draft. Some details may not match the panel yet, and screenshots are still pending. We’re publishing it as a placeholder so the structure is in place; we’ll fill in the gaps as we go.

This page covers the server-wide controls available in the WHP admin sections — restarting services, managing PHP modules and versions, and adjusting server-level configuration.

Sign in to WHP

You can sign in to WHP two ways:

1. Through your client portal (recommended). Go to https://secure.anhonesthost.com, sign in to your account, open Services → My Services, click your hosting plan, then click Login to WHP. No extra password to remember.
2. Directly with your WHP credentials. Visit https://<your-server-hostname>:8443 and sign in with the WHP username and password you set up. Your server hostname is in your welcome email and on the service page in the client portal.

Restarting services

The admin Services page lists the long-running services that run on the server: Apache (front-end web), PHP-FPM (one or more pools), MySQL or MariaDB, the mail stack, and any add-on services like Valkey or PostgreSQL if you’ve enabled them.

Each service has a status indicator and Restart, Stop, and Start controls. Restart is the safe default for picking up new configuration.

Caution

Restarting a service drops in-flight connections. For Apache and PHP-FPM, this means active web requests will fail to complete; for MySQL, in-flight transactions roll back. Pick a low-traffic window if you can.

Managing PHP modules and runtimes

WHP can run multiple PHP runtimes side-by-side (PHP 8.3, 8.4, etc.). With super admin you can:

• Install additional PHP runtimes via the PHP Versions admin page.
• Add or remove extensions per runtime — common ones (mbstring, intl, opcache, imagick, redis, etc.) are toggles; less common ones may require a support ticket.
• Edit a runtime’s php.ini from the PHP Configuration sub-page, then reload PHP-FPM to pick it up.

Switching a site to a different PHP version is done on the customer side — open Sites → your site and pick from the Container Type / PHP Version dropdown. The runtimes available there come from this admin list.

Server-wide configuration files

For settings that aren’t exposed in the panel, you can SSH to the server and edit configuration directly:

• Apache: /etc/httpd/conf.d/ for per-app drop-ins; per-site vhosts are generated from WHP and live in a directory the panel manages. Don’t edit generated vhosts by hand — they’ll be overwritten on the next config regeneration.
• PHP-FPM pools: /etc/php-fpm.d/ for runtime pool tweaks. Pool defaults are templated by WHP; edits to per-site pools are overwritten on regeneration.
• MySQL/MariaDB: /etc/my.cnf.d/. The defaults are tuned for the server’s resource profile; large-tweak changes are usually best left to a ticket so we can advise.

After editing, reload the relevant service from the WHP Services page (or via systemctl on the box).

Common admin tasks

Drop a hot file cache. From the Services page, click Reload on PHP-FPM. This is the right move after editing php.ini or an extension list.

Free disk space on a full server. Check /var/log/ first — log rotation may be lagging. WHP rotates app logs into the per-site logs/ directory; server-level logs in /var/log are yours to rotate via logrotate config in /etc/logrotate.d/.

See what’s eating resources. The admin Resource usage page shows aggregate CPU, RAM, disk I/O, and per-process drilldowns. For deeper inspection, SSH in and use top, htop, or iotop.

Troubleshooting

Service won’t restart. The Services page surfaces the systemd error; if it’s failed (exit-code), check journalctl -u <service> on the box for the underlying message. The most common cause is a syntax error in a config file you just edited.

PHP module toggle has no effect. PHP modules need a PHP-FPM reload to be picked up. The toggle should do this automatically; if it doesn’t, click Reload manually.

Edits to a generated vhost keep disappearing. That file is generated. Put your customisation in a per-app drop-in under /etc/httpd/conf.d/ instead, or open a ticket about adding a stable include hook.

Related

• Coraza WAF rules
• Users & delegated access

Still stuck?

Still stuck? Open a support ticket and our team will help.