Using Control on an existing server

Control can be installed on a supported server that already has software or websites, but installation does not automatically adopt existing hosting configuration.

Before installation

Record the services and ports already in use, especially Nginx/Apache, PHP versions, databases, Docker, DNS and SSH. Check whether another service already owns TCP 8443, 80 or 443. Take a tested backup of the server and keep independent SSH access available.

Control detects supported host components separately from Site management. Software already being installed does not make an existing website, virtual host, database or Linux user a Control-managed resource. Control does not automatically rewrite unrelated hosting configuration to make it fit.

If an existing web server, firewall or application conflicts with the management or Site ports you intend to use, resolve that conflict deliberately before moving production traffic.

Existing websites

For an existing website, the safer route is normally:

1. Create a new Control Site with the required runtime.
2. Move the application's files through SFTP, Storage or a supported Git deployment.
3. Create or attach the required database resource and move application data using the application's supported database tooling.
4. Re-enter runtime secrets in Control where required.
5. Test the new Site before changing production DNS.
6. Switch traffic only after the Control-managed Site is healthy.

Do not delete the old hosting configuration until the migrated Site has been accepted.

Existing control panels

Control does not treat cPanel, Plesk, HestiaCP or another panel's backup archive as a Control Site export. See Moving from another control panel for the supported migration model.