VMDebug offers only two ways to get in touch: email support@vmdebug.comor sign in to the console to submit a ticket linked to your order and device. Email is best for pre-sales and partnership inquiries; for running devices, node connectivity, orders, and billing, use a console ticket first.
Use email to describe your workflow, configuration, term, node, and target activation window.
Sign in to the console, submit a ticket from the relevant order, and include the order number.
Include the device ID, time of occurrence, reproduction steps, and redacted logs.
When an issue is tied to an order or device, a console ticket reduces back-and-forth verification. If you have not ordered yet or need to organize your requirements, the email generator on this page is more direct.
Compare VMDebug M4 and VMDebug M4 Pro, confirm storage add-ons and rental terms, and choose a node.
Use this for renewal status, order details, billing items, payment results, and service-term checks. Submit the ticket from the relevant order.
For SSH connectivity, node networking, macOS environments, Xcode builds, disk issues, and hardware troubleshooting.
For enterprise procurement, compliance documentation requests, bulk device needs, and long-term workload planning. All partnership inquiries use the support email.
This form does not submit data to the website server. When complete, it opens your system email client and organizes the fields in the message body; you can still review and edit everything before sending.
If you already have a device, paste the organized details into a console ticket. The email generator can also help you prepare information in advance, but do not include access tokens, private keys, passwords, or complete payment details in logs.
Enter order and billing issues through the console so the ticket is linked to the relevant order. Support checks order records, terms, billing items, and payment status; your account password or payment secrets are not needed.
Copy the number shown in the order details; do not provide only the device nickname.
Select order status, billing item, payment result, renewal, or order closure.
Include the time zone and state whether the issue occurred during ordering, payment, or renewal.
Specify whether you need a status check, an item explained, or a verifiable record corrected.
Support replies prioritize actionable checks, required evidence, and next steps. Coverage depends on whether the issue occurs on the device, node, system environment, or an external service.
We provide verification guidance across the current two plans and add-ons based on your workflow, memory pressure, storage scale, concurrency, and term.
Required details Task type, concurrency, data volume, and target termWe check device status, host fingerprints, SSH paths, port requirements, routing symptoms, and prerequisites for remote graphical access.
Required details Device ID, node, source network, time of occurrence, and error messageWe investigate reproducible symptoms involving disks, memory, network interfaces, or external devices and link the specific device through a console ticket.
Required details Device ID, system information, diagnostic output, and impactWe can help verify the runtime environment, log collection, and network conditions, but software licensing, external platform availability, and app review results are determined by the relevant service provider.
Supported areas Environment reproduction, log analysis, and basic dependency and network checksFirst determine whether the issue involves configuration, connectivity, the device, an order, or a third-party toolchain.
Verify that the time, device or order ID, reproduction steps, and redacted logs are consistent.
We reply with actionable checks, requests for additional materials, or the next processing status in the console.
Connection, environment initialization, and billing definitions are covered in dedicated documentation. Record the results there first, then submit a ticket so support can continue directly from the step that failed.
Review the steps for first connection, network diagnostics, Xcode, CI/CD, storage, and system recovery.
Open support guides Q AND AReview physical resource types, two configurations, four terms, 5 nodes, payment methods, and usage boundaries.
View frequently asked questions ONBOARDINGComplete configuration selection, connection verification, toolchain migration, dependency recovery, testing, and archive validation in order.
View the onboarding path CONTROLSign in to the console, select the relevant instance or order, and view ticket queue, additional-material requests, and processing status.
Go to the consoleInclude your workflow, configuration, and activation time in emails. For tickets, link the device or order and include the time of occurrence, reproduction steps, and redacted logs.