EzePanel · Knowledge base
Find a useful next step for a hosting problem.
Start with the symptom, understand the relevant boundary and open the guide for the tool that owns the work. These practical answers complement the structured documentation.
Find your symptomWebsites & PHP
My website does not open over HTTPS.
Check which hostname is affected, whether it resolves to the intended server and whether the certificate covers it. SSL issuance, HTTPS redirection and application health are separate checks.
Open DNS & SSL to review the account-owned domain and certificate workflow. Keep the exact non-sensitive error and time for the provider if the problem continues.
Feature overviewA PHP change finished, but the site still fails.
Confirm the intended domain and effective runtime. The job result does not prove the application supports the selected PHP version or has every required extension.
Review the application error and prior working configuration. Use PHP & MultiPHP for the change scope, and involve the provider when the required runtime is unavailable.
Feature overviewJobs & recovery
A background job is still queued.
Record its identifier, type, scope and age. A waiting job may depend on a worker, resource gate or service that the hosting provider maintains.
Use the owning feature’s history. Repeated requests can duplicate work; investigate the reason before submitting another data-changing operation.
Feature overviewI restored files but the database is unchanged.
The customer file-restore action does not automatically import SQL. A website recovery needs the matching files, database and application configuration.
Choose the intended database and a usable SQL recovery copy. Review the import result and test the application; failed imports are not guaranteed to roll back every change.
Feature overviewAccess & scheduled work
The browser terminal is unavailable.
Panel sign-in and shell capability are different. The provider controls browser terminal enablement, shell mode, account status and backend availability.
Review the reported prerequisite and ask the provider about the account policy. Normal account shell access is not root access; never share a private SSH key to request enablement.
Feature overviewA scheduled command behaves differently from the website.
Cron can use a different interpreter, environment and working directory. Use explicit paths and deliberate application logging, and confirm the scheduling timezone.
Plan for overlap and failure inside the application. Cron Jobs manages the schedule; it is not a complete execution-history or automatic application-repair service.
Feature overviewProvider operations
The server dashboard looks healthy, but a customer reports an outage.
First check observation freshness. A server snapshot, an active service and a working website are different pieces of evidence.
Use Central Monitoring and Server Health to narrow the incident, then verify the specific website. An acknowledged alert or completed action does not independently prove resolution.
Feature overviewMy hosting-plan request has not changed the limits.
A request goes through provider review. Approval, application and effective-policy verification are separate stages, and a preferred date is not guaranteed activation.
Follow the request history and contact the hosting provider. Its hosting packages are separate from an EzePanel software subscription.
Feature overviewCommon questions
Finding the right help.
Is this the complete product documentation?
No. This page collects practical starting points. Documentation organizes the full product and installation guides by area.
Who should a hosting customer contact?
The hosting provider responsible for the account is normally the first contact. EzePanel software support serves the separate product relationship.
Should I paste credentials into a troubleshooting request?
No. Share the symptom, time, error and relevant sanitized context. Keep passwords, private keys and recovery codes private.
Does following an answer automatically change my server?
No. These are explanations and links. Any action in the panel still follows its own permissions, scope and verification requirements.
Bring the right context to support.
Share the affected service, release and non-sensitive error details so the responsible team can understand the situation.