Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Webmin TLS Certificates: Administration Interface Versus Apache Sites

Published

WebminSSL

Installing a certificate for the Webmin administration interface is different from using Webmin to configure an Apache website. The previous article described the Apache task under a Webmin-interface title; choose the endpoint you actually need to secure.

Webmin’s own administration interface

With authorized access, use Webmin > Webmin Configuration > SSL Encryption. Review the current certificate and hostname before changing settings. Back up the existing configuration and retain a secure alternative administration route in case a certificate/key path or listener change fails.

  1. Confirm the exact administration hostname, port and any reverse proxy. Port 10000 is common, not universal.
  2. Use the supported certificate/key configuration or available issuer workflow for the installed version. Protect private-key files and provide the required chain.
  3. Apply the intended change and follow the version’s restart/reload requirements. Do not disable TLS to work around a certificate error.
  4. Reconnect with the expected hostname and verify the presented certificate without bypassing warnings. If a proxy terminates TLS, check that endpoint and its protected origin route separately.

An Apache website managed through Webmin

For an actual website, use Servers > Apache Webserver and the correct existing virtual host. Do not create a duplicate wildcard port-443 virtual host merely to follow an old example. Configure that site’s certificate, matching key and chain, validate the Apache configuration and perform a controlled reload.

That does not change Webmin’s own certificate. Likewise, changing the administration certificate does not secure every hosted website or mail service.

After the change

Verify renewal ownership, expiry alerts and each affected endpoint. Keep administration access restricted to authorized users/networks; a trusted certificate does not replace access controls or updates. Do not upload keys to a public document root.

References: Webmin’s SSL Encryption settings; separate Apache module.

Reviewed October 15, 2026. No administration listener, Apache virtual host or customer key was changed.

Related guides

Account services are unavailable until the production backend is configured.