Billing, Support, and Logs
Use business and evidence tools without changing hosting resources.
1Overview
Billing opens the connected billing portal, Support records and follows requests, and Logs exposes server or account event evidence for troubleshooting.
2Before you begin
Administrator actions can affect multiple customer accounts and server services.
3Step-by-step workflow
Open the relevant section, use the portal or ticket action for customer-facing work, and filter logs by account, domain, service, or time before collecting evidence. Attach only the minimal relevant output to a ticket.
- Use Billing & Plans for service and plan information, Help & Support for assistance, or Logs for technical evidence.
- Confirm the server, account, and domain involved in the request.
- For billing, open the linked client area and sign in to its separate account.
- For support, record the error message, incident time, affected URL, and steps that reproduce the issue.
- Open the relevant log and narrow it to the incident period.
- Reproduce the issue once when safe and compare the new log entry with the reported problem.
- Remove passwords, API tokens, private keys, personal data, and unrelated entries before sharing evidence.
- After a fix, repeat the original check and confirm the error is no longer present.
4Practical example
Example: a hosting-panel administrator login and the billing client-area login can be different accounts. A billing problem should be raised against the affected service in the client area.
5Verify the result
Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.
- Confirm the ticket, billing action, or log filter reflects the requested account.
- Remove copied sensitive values from notes before sharing externally.
6Common problems and what to check
The billing page asks for another login: use the client-area account associated with the service.
A log appears empty: check the selected website, log type, and time range.
Support cannot reproduce a problem: provide the precise URL, time zone, browser/client, and error text without sharing a login password.
7Security, impact, and rollback
Logs can include paths, addresses, and error detail. Limit access to authorized staff and redact secrets before sharing diagnostics externally.