EzePanel · Initial server setup
Give your EzePanel server a deliberate first setup.
Confirm the server identity, administrator, provider branding, DNS defaults and notification email through the six-step setup workflow.
Read the guideBefore the first login
Use the server and administrator access supplied through the approved installation process. Keep independent server access available and confirm the supported operating system and release.
The setup wizard configures an installed panel. Obtain your installer and activation key separately through the authenticated customer portal.
Server identity
Review the detected operating system, architecture, CPU, memory, disk, hostname, addresses and timezone. Enter the server display name, fully qualified hostname, IPv4 address and optional region.
Hostname and timezone changes use the supported system helper. Earlier successful host changes can persist if a later step fails; review the current state before retrying.
Administrator account
Confirm the existing administrator’s display name, username and email. The wizard edits that account rather than creating another administrator.
A password change signs the administrator out of existing sessions. Sign in again to resume. Sensitive settings require current administrator verification and MFA/recovery verification when enabled.
Company and hosting identity
Set the provider name, optional HTTPS website, support email and footer text used by supported panel branding and notification surfaces.
These identity fields do not configure the hosting provider’s support staffing, response commitments or software licensing rights.
Hostname and DNS
Confirm the hostname and entered IPv4 address, plus optional IPv6. Review the detected DNS service state and use Check DNS for a resolution observation.
Check DNS does not save settings. A warning can be continued past; that is not proof that public DNS is correct. External DNS and registrar changes remain separate.
Nameserver defaults
Set different primary and secondary nameserver hostnames and their addresses. These defaults are used for new hosted zones.
Existing zones are not rewritten by this setup step. Create registrar glue records where required and verify public delegation separately; two names alone do not establish independent DNS infrastructure.
Notification email
Configure the sender identity, SMTP host, port, encryption and authentication. Keep certificate verification enabled for secure notification transport.
Save & test SMTP saves settings and checks connection/authentication; it sends no email. Finish without changing SMTP leaves the existing settings unchanged. This step does not create customer mailboxes or reconfigure mailbox hosting.
Finish, then verify the service
Review saved settings and the resulting panel access. Verify hostname resolution, intended nameserver delegation and the actual notification-delivery path before relying on them.
Skipping setup retains already saved settings and allows later review. Setup completion records progress; it is not a universal production-readiness certification.
Common questions
Before you finish setup.
Can I skip the first-run setup?
The workflow supports confirmed skipping and retains already saved values. Unconfigured nameservers or notification email still need attention later.
Does the SMTP test send a message?
No. It tests connection and authentication after saving. Verify actual delivery separately through the appropriate notification workflow.
Will changing nameserver defaults rewrite every zone?
No. These defaults apply to new zones; existing hosted zones are not rewritten by this step.
Why did I need to sign in again?
Changing the administrator password revokes sessions. Sign in with the updated credentials to continue.
Bring the right context to support.
Share the affected service, release and non-sensitive error details so the responsible team can understand the situation.