Order and host status
Verify the order ID, rental term, host status, and delivery details. New purchases, renewals, and host management are handled in the console; the console’s live status is authoritative.
Start with a status check
Identify the issue first, then submit actionable details.
For MiniDebug Cloud Mac setup, connections, system login, Xcode builds, storage add-ons, renewals, and release workflows. Complete the local checks on this page first, then submit order context and redacted logs through a console ticket.
Support scope
First determine which layer is affected.
Remote connection failures, build failures, and order-status issues can look similar, but they require different entry points. All six categories below can be reported through a console ticket.
Node and remote access
Troubleshoot addresses, ports, network paths, and remote sessions across Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Eastern United States.
System login and permissions
Check first login, credential updates, SSH keys, graphical-session permissions, and account access scope. For collaboration, use separate, traceable credentials.
Build environment
Diagnose xcodebuild or fastlane tasks by checking the Xcode version, command-line tools, dependency caches, signing materials, disk space, and build logs.
Storage add-ons
Confirm the storage capacity selected in the order, mount status, available space, and task directories. If storage is low, clear regenerable caches first, then decide whether to adjust the configuration.
Renewal and release
Before renewal, verify the term and add-ons. Before release, back up code, certificates, models, assets, and build artifacts, and confirm that automation has stopped writing data.
First-time setup path
Complete your first connection check in five steps.
Do not start with a saved old address. Use the host status and connection details shown in the console for each order.
-
01
Input: Order ID
View order and host status
Sign in to the console, open the relevant order, confirm the model is MiniDebug M4 with M4, 16GB RAM, and 256GB SSD, and note the selected node. If the host is not yet ready for connections, do not repeatedly attempt remote login.
-
02
Output: Connection parameters
Get this order’s connection details
Copy the destination address, port, account, and supported connection methods. Save the address and port together; do not mix SSH parameters with VNC or screen-sharing parameters.
-
03
Verify: Host identity
Complete the first system login
Start the connection from a trusted local device whenever possible. Verify the host fingerprint on the first SSH connection; for graphical access, confirm that the target node matches the order, and never save credentials on a shared device.
-
04
Action: Update credentials
Update credentials and access scope
Update the initial credentials immediately after login; use keys for SSH automation whenever possible. Limit authorized team members and avoid sharing one account long term or placing plaintext passwords in scripts.
-
05
Result: Baseline environment ready
Verify the network and build baseline
Check repository access, DNS resolution, disk space, the Xcode path, and command-line tools. Run lightweight validation commands first, then fetch full dependencies or start a time-consuming build.
Build failure triage
Start with the first stable, reproducible error.
The final log lines usually only show that the task stopped. Look upward for the first consistently occurring error, classify it into one of the six categories below, and then decide whether to change the project or submit an infrastructure ticket.
Separate identity, target, and export stages
- Confirm that the build target, Bundle Identifier, and signing configuration match.
- Check whether the archive succeeds but fails during export.
- Record the first signing error and the 20 log lines before and after it.
Recommended action: Verify the project signing settings first. If signing materials cannot be read, then check file permissions and the automation injection path.
Check validity, matching, and read permissions
- Confirm that the required files are located where the current task actually uses them.
- Check that the certificates, provisioning profiles, and target environment match.
- Do not include passwords, original certificate files, or complete keys in a ticket.
Recommended action: First verify access in an interactive session, then reproduce the automated task and compare the environment variables and execution account.
Use the same toolchain in the GUI and command line
- Record the Xcode version, SDK version, and target platform.
- Run
xcode-select -pto verify the current path. - Check whether the CI process inherited the expected developer directory.
Recommended action: Pin the version and path first, then clear derived data that is incompatible with the new version. Change only one variable at a time.
Verify the lockfile before clearing caches
- Keep the dependency lockfile and record the package-manager version.
- Compare a build from a clean directory with one that hits the cache.
- Clear only regenerable directories; do not delete unbacked-up project files.
Recommended action: Confirm cache issues by reproducing them with an empty cache; record network download failures separately with the target, time, and error code.
Check total capacity, free space, and large directories
- Check usage from the working directory, derived data, archives, and dependency caches.
- Confirm whether logs and temporary files are continuing to grow.
- Before cleaning, confirm that artifacts are archived and recoverable elsewhere.
Recommended action: Delete regenerable caches first; verify long-term capacity needs against storage add-ons in a later order.
Keep the command, time, and first error
- Include the trigger, working directory, and the complete redacted command.
- Record when the issue occurred and specify the time zone.
- Also provide the expected result, actual result, and reproduction frequency.
Recommended action: Submit text logs rather than screenshots alone. Remove repository tokens, upload keys, passwords, and source-code excerpts.
Connection troubleshooting tree
Check in order; do not skip upstream conditions.
These seven checks form a dependency chain. If an upstream check fails, downstream client settings often will not change the outcome.
-
01
Continue after passing
Host status
Confirm the order and host status in the console. If the status differs from expectations, record the order ID and displayed result, then submit a ticket.
-
02
Confirm target match
Destination address
Copy the connection address for the current order exactly. Rule out extra spaces, old addresses, and local hosts overrides, and confirm that you are not connecting to another order.
-
03
Record error type
Port and connection method
Confirm that SSH, VNC, or screen sharing uses the corresponding port and client. Record timeouts, connection refusals, and authentication failures separately.
-
04
Complete network comparison
Local network
Test with the same parameters from another trusted network to determine whether a corporate egress, proxy, or carrier path affects the connection. Do not expose credentials during testing.
-
05
Confirm outbound rule
Firewall rules
Check whether the local device and organizational network allow outbound access to the target port. Do not disable all protection for troubleshooting; verify the smallest necessary scope.
-
06
Authentication result clear
Account permissions
Distinguish successful network connectivity from successful account authentication. Confirm the account name, key permissions, graphical-login permissions, and whether credentials have been updated.
-
07
Keep retry result
Session usage
Check for unfinished graphical sessions, duplicate automation tasks, or resource usage. Safely exit old sessions first, then perform one controlled retry.
Ticket information template
Submit enough reproducible context in one request.
Console tickets are suitable for issues involving existing orders. If you cannot sign in to the console, use the only supported email address, support@minidebug.com, and provide the required account verification details.
Recommended ticket structure
Copy the field names and complete each one
- Order ID
- The order ID shown in the console; do not submit payment credentials.
- Node
- Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or the Eastern United States.
- Time of occurrence
- State the date, time, and time zone, and indicate whether this happened once or is recurring.
- Reproduction steps
- Number the steps in the actual order, starting with opening the console, running the command, or launching the client.
- Redacted logs
- Include the first error and its context. Remove passwords, tokens, private keys, and sensitive project content.
- Expected vs. actual
- Describe separately the expected result, actual result, and whether the issue reproduces consistently.
Existing order
Create a console ticket
Use a console ticket
Tickets retain order context and are suitable for host status, node connectivity, add-ons, renewals, and release issues. Complete the relevant troubleshooting steps before submitting.
Unable to sign in
support@minidebug.com
Send a support email
Put the issue type and order ID in the subject. Use the field structure on the left in the message body. Copy the address directly if needed.
Response boundaries
Issue ownership determines the next step.
We assess whether an issue concerns the physical node, macOS usage, project code, or an external dependency, then provide the next verification direction.
Node infrastructure issues
This includes abnormal host status in the console, connection details that do not match the order, node reachability issues, and order configuration that does not reflect the selected options.
- Provide the order ID, node, and time of occurrence.
- Attach connection comparison results from different local networks.
- Record the console status and client error type.
macOS usage issues
This includes system settings, file permissions, shell environments, disk cleanup, remote-client parameters, and local account permissions.
- Reproduce the operation in a controlled session first.
- Record the system version, execution account, and target path.
- Submit the error text, not just a UI screenshot.
Project code and build configuration
This includes compile errors, test failures, signing configuration, dependency-version conflicts, script paths, environment variables, and application runtime logic.
- Reproduce the first error with minimal changes.
- Compare toolchain differences between the local and Cloud Mac environments.
- Have the project maintainer modify the code or pipeline configuration.
Third-party service issues
This includes authentication, rate limiting, or server errors returned by code hosting, dependency mirrors, package registries, notification systems, and upload targets.
- Confirm the target service status and account permissions.
- Record the response code, request time, and retry results.
- Submit redacted logs to the relevant service provider.
Self-service resources
Read the relevant guide first to avoid duplicate requests.
Guides for connection parameters, pricing, data protection, and common build issues are available separately. If the checks in a guide do not resolve the issue, include the results in your ticket.
Remote access
Compare SSH, VNC, and macOS screen sharing, troubleshooting connections by latency, bandwidth, and session status.
FAQ
Check device type, rental term, node, add-ons, payment methods, build tools, and data-processing boundaries.
Security and reliability
Learn about dedicated physical-node isolation, credential management, remote-access protection, data lifecycle, and responsibility boundaries.
Plans and pricing
View MiniDebug M4’s fixed configuration, four rental terms, storage add-ons, Thunderbolt 5 linking, and node matrix.
Contact and routing
Distinguish pre-sales configuration questions, existing-order issues, connection failures, build-environment problems, security questions, and partnership inquiries.
Prepare your order context, then take the next step.
New purchases, renewals, and host management are handled through the console; submit existing-order issues through a console ticket first. Payment supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All orders are settled in USD; actual gateway availability is returned by the backend interface.