Connection failures, credential errors, Xcode environment changes, storage usage, network access, and billing questions each follow a dedicated path. Complete the six quick checks first; if the issue persists, include your order, node, timestamp, and reproduction steps in a console ticket.
Each path starts with information you can verify now, without guessing the root cause. If several symptoms occur together, check the order status, device power status, and connection path first.
For timeouts, connection refusals, interrupted sessions, or unavailable graphical interfaces. Check the node address, port, local network egress, and selected remote access method first.
View the connection guideFor failed logins, unclear credential status, or missing order details. Do not repeatedly try old information; first confirm in the console that the order and connection details belong to the same device.
Check the order and credentialsFor version mismatches, certificate import failures, signing errors, interrupted Fastlane runs, or failed artifact exports. Keep the complete error stage, but remove sensitive fields before submitting it.
Troubleshoot the build environmentSeparate project files, dependency caches, build archives, model files, and temporary output. Do not delete unknown directories directly; record the path, space used, and related task first.
Review storage checksCheck local egress, the target port, DNS resolution, and project dependency sources. If the same node behaves differently on different networks, record the results from both environments.
Check connection and networkPrepare the order number, selected rental term, node, and add-ons. Checkout supports USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only, with all amounts in USD.
View order and billing detailsRecord the results in order. Each check narrows the troubleshooting scope and prevents local networking, connection methods, and device status from being conflated.
Confirm that the order is still within its valid rental term and that the order number you are viewing matches the current device. If the page status changes, record the actions taken before and after the change.
Verify the Singapore, Japan (Tokyo), South Korea (Seoul), or Hong Kong node, along with the address and port returned by the console. Do not infer the current address from historical connection records.
Check whether the device is available for connection. If you recently restarted it or installed a system update, record the time and wait for the console to return the latest device status.
Confirm that the current network allows access to the target port. Under controlled conditions, compare with a trusted network and record whether the same timeout occurs.
Distinguish between command-line access, graphical interfaces, file transfers, and automated tasks. Different methods use different ports, client settings, and error messages.
Confirm that you are using the latest connection details for the current order. Do not paste passwords, keys, or complete access credentials into public screenshots or email subjects.
“Build failed” is not a sufficiently specific ticket subject. First identify whether the failure occurred during dependency installation, compilation, testing, signing, archiving, or artifact export.
Record the current version, the project-required version, the command-line tools path, and the task where the difference first appeared. In multi-version environments, also confirm the actual path used by automation.
Confirm the imported item, keychain location, access permissions, and certificate validity. A ticket only needs the redacted name and error text; do not upload a certificate private key.
Record the target, build configuration, failure stage, and key error lines. Describe project code issues separately from cases where the environment cannot access signing materials.
Specify the lane name, trigger method, stopping point, retry result, and log location. If manual execution succeeds but automation fails, provide the differences between both paths.
Confirm that archiving completed, the export directory is writable, enough disk space remains, and no interruption occurred during artifact transfer.
Model loading failures, interrupted inference, and disconnected sessions can originate at different stages. Monitor the environment, file locations, memory changes, output directory, and session persistence together.
Record the Python environment, MLX version, launch command, and dependency installation result. If the same script ran successfully before, note recent environment or code changes.
Confirm the model size, actual storage path, cached copies, and output directory. If a download is interrupted, keep the temporary-file status to avoid repeated downloads consuming more space.
Record memory changes before loading, after model loading, and during task execution. If the task is terminated, note the batch size, context size, and resource state before stopping.
Separate task execution from local connection interruptions. Use a resumable session method, continuously write logs and output files, and check the process status first after reconnecting.
The knowledge base is automatically sorted by publication date and grouped by month. Date markers on the left locate each month, while the content area on the right shows that month’s articles; month headings consistently use the “YYYY Month” format.
Covers MLX environment checks, model storage planning, and cache, disk, and port management for container development on Cloud Mac.
Covers remote creative workflows, SSH tunnels, and Fastlane automation, documenting the complete path from connection verification to artifact delivery.
Covers device naming, permission assignment, environment baselines, asset records, and node handoffs for parallel multi-project work.
The closer your description is to a reproducible record, the easier it is to determine whether the issue involves the node, system access, software environment, or project task. For existing orders, submit through the console whenever possible so the order and device status can be linked.
Provide the order number and the actual node: Singapore, Japan (Tokyo), South Korea (Seoul), or Hong Kong.
State when the issue first appeared, when the service was last working normally, and when retries took place.
List the connection method, commands, or interface actions in execution order, and identify the step where the error appears.
Attach key error text or redacted screenshots. Show only the areas needed to diagnose the issue, without complete addresses or access details.
Tickets, emails, and screenshots must not contain login passwords, keys, certificate private keys, recovery codes, complete access credentials, or complete payment credentials.
Send an email to support@rentmymini.com. Put the inquiry type in the subject and include a reachable email address plus the necessary redacted information in the message.
The support queue categorizes requests by order, node, connection path, and reproduction details. The four issue types below require different evidence and follow different handling paths.
| Issue layer | What RentMini can verify | What the user should provide | Recommended entry point |
|---|---|---|---|
| Node availability | Order association, node status, device status, and service-side connection information | Order number, node, time of occurrence, and console status | Console ticket |
| System access | Connection details, remote access path, device response, and credential status | Connection method, error stage, and local network comparison results | Connection guide |
| Third-party software configuration | Whether the Cloud Mac system can successfully install, launch, and access files for the software | Software version, installation method, configuration steps, and redacted logs | Contact the service team |
| Project code issue | Help distinguish the boundaries between the device, system environment, and project task | Minimal reproduction, dependency versions, failed step, and project-side changes | Knowledge base |
Console tickets retain the issue description, additional materials, and follow-up records. Continue adding results to the original ticket instead of splitting one issue into multiple unlinked requests.
When the node, error behavior, network environment, or reproduction steps change, describe the change in the original record. Re-sending the same screenshots does not add actionable information.
State the affected order and the task that currently cannot be completed in the subject, and include the minimum diagnostic results. The support queue classifies requests by impact and reproducibility.
RentMini offers two Cloud Mac configurations, RentMini M4 16 and RentMini M4 24, starting at $19.4/day. Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong are all available in the catalog; live availability is shown in the console.