Route first, then add context

Send your issue to the right channel.

Email us about pre-sales configuration, security and privacy, or partnerships. For existing orders, node connections, and build environments, sign in to the console and submit a ticket so we can link it to host status and support history.

Rent a Mac mini M4 now Sign in to submit a ticket

Two ways to contact us

Choose based on whether you already have an order.

Support email

Best for pre-sales configuration, security and privacy, partnership inquiries, and account issues when you cannot sign in to the console.

support@minidebug.com Weekday target: first reply within 24 hours

Console tickets

Best for existing orders, host status, connection issues, storage add-ons, renewals, and build-environment troubleshooting.

Open the ticket portal Node connection issue target: first response within 4 hours

Issue routing

Start by selecting what you need help with.

You’ll see the recommended channel and matching information generator after making a selection. Form content is organized only in your browser and is not sent to our servers.

Recommended now: email your pre-sales request with your workflow, concurrent tasks, rental term, and preferred node.

Structured email generator

Reduce back-and-forth in the first email.

Your entries are organized only in this browser. Click the button to open your system email app, then continue editing before sending.

Pre-sales and general inquiries

Generate a pre-sales inquiry email

For configuration questions, security and privacy issues, and partnerships. Configuration recommendations cover only the currently available MiniDebug M4.

Inquiry type

Target workflow

Expected concurrent tasks

Planned rental period

Preferred node

Storage requirements

Expected start date

Reply email

Project background and constraints

Fixed available configuration

MiniDebug M4

ChipM4
Memory16GB RAM
Storage256GB SSD
Device typeDedicated physical machine, not a virtual machine

Check the full plan price

Five available nodes

Consultations match the catalog

Consultations cover orders for Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US East only. Actual availability is determined in real time by the console.

Select a node and order

Existing orders and technical troubleshooting

Generate a technical issue summary

We recommend pasting the summary into a console ticket first. If you cannot sign in temporarily, you can also contact the support team using the generated email.

Issue type

Order ID

Device model

Node

Current system status

Time the issue occurred

Reproduction steps

Expected result

Actual result

Redacted log attachment The generator does not read or upload files. After your system email app opens, manually attach logs with tokens, private keys, passwords, and source code removed.

Recommended channel

Submit a ticket first for existing orders

Tickets keep the order ID, node, reproduction steps, progress, and additional logs together, making them suitable for issues requiring multiple rounds of troubleshooting.

Submission order

Start with facts, then add your assessment

01
Identify the target
Order ID, device model, and node.
02
Fix the timeline
Record when the issue occurred and the current status.
03
Provide evidence
Include reproduction steps, expected and actual results, and redacted logs.

View the troubleshooting path first

Response and handling boundaries

Different issues require different context.

The first response means your issue has entered the queue and verification has started; it is not the final resolution time. Complex issues may require additional reproduction details.

Within 24 business hours

Pre-sales, security, privacy, and partnership email

The first reply confirms whether your request is complete and identifies any workflow, concurrency, rental-term, node, or data-handling details needed. Issues involving specific order status will be directed to a console ticket.

Target: within 4 hours

Node connection tickets

For cases where the console shows the node online but SSH, VNC, or screen sharing cannot establish a session. Include the node, time of occurrence, local network tests, and redacted error details.

Within 24 business hours

Build environment and project issues

The support team first distinguishes between the host base environment, Xcode version, dependency cache, disk space, and project configuration. Project code logic must still be assessed by the project maintainer using complete build logs.

Operating normally year-round

Node infrastructure issues

All five nodes operate normally 365 days a year. If the host online status, connection entry point, or node infrastructure is abnormal, submit a ticket directly rather than sending a brief email without order context.

Before you send

Submit only the minimum information needed for troubleshooting.

The support team typically needs only the order ID, node, time of occurrence, reproduction steps, expected result, actual result, and redacted logs. Do not include sensitive credentials that could directly access a host, repository, or payment tool in an email or ticket.

Keep essential identifiers

Order ID, node, time, and error codes may be retained.

Capture relevant logs

Keep only the necessary sections around the issue and remove environment variable values.

Describe reproducible steps

Use ordered actions and commands; do not write only “cannot use.”

Separate expected from actual

State clearly what should have appeared and what appeared instead.

Order actions do not go through the contact page

For new purchases, renewals, and host management, go directly to the console.

The contact page adds context for inquiries and troubleshooting; it does not replace the order workflow. Payment supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), with all charges settled in USD. Available payment gateways are determined by the console.

Select a node and order Manage existing hosts