Appearance
Manage a Site
WebOpen ZynoHosting, select a site, and use the overview for status and the actions your role allows.
Site overview
The overview can show the site's address, aliases, TLS state, runtime, storage use, database status, deployment state, and recent hosting operations. A warning or pending state means a change is still applying or needs attention.
Common actions
| Action | How it works |
|---|---|
| Manage hostnames | Add or review an authorized hostname, then complete the DNS instructions shown by the portal. Domain evidence and certificate status update as verification progresses. |
| Deploy files | Use the file tools or the CLI to plan and apply an authorized deployment. Confirm the selected site before applying a deployment. |
| Manage WordPress | WordPress sites can show install status and approved actions such as an administrator sign-in link or password reset. Treat one-time sign-in links as sensitive. |
| Manage files | Create, replace, download, or delete files only within the site's document root. If the portal reports a concurrent update, refresh and retry with the current file version. |
| Manage database access | Review the managed database and use the available credential, export, or maintenance actions. Existing database passwords remain hidden after they are set. |
| Manage SFTP | Review connection instructions, add or remove an approved SSH key, or rotate a password when your role allows it. Password values remain hidden after they are set. |
| Clear cache | Request a cache purge after a deploy or content update. A purge completes independently from a deployment. |
| Redirects and WAF rules | Manage approved redirects and manual allow/block rules when your role allows them. ZynoHosting protects reserved platform paths, so a redirect cannot take over those paths. |
| Analytics and ZynoThreads | Attach the site to one compatible active analytics property, choose an optional collection-mode override or cross-site participation, enable the separately deployed analytics feature, and configure an eligible ZynoThreads web integration. |
Storage, cache, and reconciliation
The site overview reports storage quota state, measured usage, available space, and whether the configured state has applied to the cluster. Storage limits are organization-controlled; contact a platform administrator when the site needs a quota change. A quota warning does not increase the limit or delete files automatically.
Pick a cache policy your role allows, then request a purge after content or deploy changes. Purge and deploy are separate—check each status before assuming visitors see the new site.
After you save, ZynoHosting applies the change in the background. The overview shows pending, applied, or failed status. If something fails, keep the error text when you contact support.
Redirects and WAF rules
Use redirects to send a matching request to an approved destination and use WAF rules to add a manual allow or block rule when your organization gives you those controls. Review the hostname, path, and destination carefully before saving. Reserved ZynoHosting paths remain protected and do not become redirect destinations.
Delete or disable a rule that is no longer required. If a redirect or WAF change has a pending or failed operation, correct the displayed configuration and wait for the reconciliation result before testing the live site.
Analytics and ZynoThreads
The site can connect to one compatible active analytics property. The property controls shared reporting and privacy settings, while the site can override collection mode and choose whether to participate in cross-site behavior. The separately managed analytics feature must also deploy successfully before the site collects data. Use the Analytics area to review the available overview, traffic, path, audience, or journey information for your authorized property. See Hosting Analytics for property, site, privacy, retention, and cross-site setup.
When your organization enables ZynoThreads web integration for a site, use the site's integration controls to select the qualified configuration. A site association and integration change can apply in the background; confirm its status before publishing related site changes.
Backups and deletion
If your role offers the action, request a complete backup archive before deleting a site. Deleting a site removes its site home, so download and verify any archive you need before confirming deletion. The site page reports the deletion operation until it completes.
Troubleshooting
| Problem | What to check |
|---|---|
| A saved change is not live | Check the operation status on the site overview. A pending or failed operation needs to finish, retry, or be corrected before the serving configuration changes. |
| A deployment is blocked | Confirm that your account can deploy to the selected site and that the plan identifies the intended files. |
| A file action fails | Confirm the path is within the site's document root and refresh if another update changed the file. |
| TLS is not active | Complete the domain's DNS verification and inspect the domain status for the specific missing record or conflict. |