Support tickets
Top nav support — org-wide, not project-scoped. Path:
/o/your-org/tickets. Use for billing questions, technical
issues, abuse reports, and feature requests.
Ticket list
Tabs:
- open — everything except closed and resolved (default).
- closed — closed and resolved tickets.
Table: subject, status, priority, category, last activity. new ticket on the open tab.
Status labels
open, needs reply, with staff, resolved, closed
Priority
low, normal, high, urgent
Category
general, technical, billing, abuse, feature request
Open a ticket
new ticket modal fields:
- subject
- category
- priority
- related vm (optional) — picker lists VMs across all org projects
- details — markdown, up to 20,000 characters
From a VM or bare-metal lease
VM or bare-metal overview → report an issue opens compose with technical category and the resource pre-selected.
From an error
When something fails on our side — an internal error, a datacenter that can't be reached, or no capacity — the error message offers open a ticket. It opens compose with the subject prefilled and the error attached, so support can find exactly what happened without you copying details. Errors you can fix yourself, such as a missing field or a quota limit, don't show the link.
Ticket thread
Click a subject to open the thread. Messages show as you, metalhost staff, or system (markdown rendered).
- Open tickets: reply box + send reply
- close ticket — optional final note
- Resolved/closed: read-only; open a new ticket if you need more help
Thread auto-refreshes about every 15 seconds.