First determine whether the issue involves connection, builds, permissions, storage, billing, or service status. Then collect node details and error output in order. For existing orders, sign in to the console to submit a ticket.
Do not change the network, toolchain, and permissions at the same time. Change one condition at a time and record the before-and-after results to identify the real cause.
Check the node address, remote access method, initial credentials, and client version first. Confirm the keyboard layout and resolution before transferring code, certificates, or media assets.
View connection stepsRecord the client name, network type, time of occurrence, and whether command-line access works. Rule out local network instability first, then adjust display settings or establish a new session.
View connection troubleshootingKeep the command and complete exit code, then check disk capacity, certificate validity, Keychain permissions, dependency caches, and the Xcode version in order.
View build troubleshootingCheck the execution user, working directory, environment variables, secret access scope, and cleanup scripts. Compare the actual environments used by the interactive shell and automation process.
View command examplesUse system commands to confirm volume capacity and free space, then check the +1TB SSD or +2TB SSD add-on in the order. Do not estimate remaining capacity from the project directory alone.
View add-on pricingPrepare the order number, rental period, model, node, add-on quantity, and payment method. The amount due and available payment gateways are determined by the console in real time.
View billing helpDelivery details confirm the node and access method, but stable builds also depend on a consistent toolchain, permissions, and dependencies.
Confirm that the order number, node region, host address, and delivered remote access method all refer to the same Cloud Mac.
Check that the current user can access the project and build directories and the required system settings. Avoid expanding permissions unnecessarily.
Check keyboard mapping, display scaling, clipboard requirements, and session reconnection behavior. Confirm a safe exit before starting long-running tasks.
Save the macOS, Xcode, command-line tool, and package manager versions. Use this baseline to reproduce the environment during later troubleshooting.
Start with the smallest project or a test branch to verify dependency installation and the build directory before moving certificates, caches, or large assets.
“Build failed” is not enough to locate the issue in a ticket. Copy the key output before and after the failed command, and state whether the same command can be reproduced in an interactive session.
$ ssh build-user@node-address
Last login: current session
$ sw_vers
ProductName: macOS
ProductVersion: [current system version]
$ xcodebuild -version
Xcode [currently installed version]
Build version [current build number]
$ xcodebuild -workspace Project.xcworkspace \
-scheme Project \
-configuration Release \
-destination "generic/platform=iOS" \
archive
note: Resolving package dependencies
note: Compiling target Project
error: Build input file cannot be found
** ARCHIVE FAILED **
exit status: 65
$ bundle exec fastlane ios build
[fastlane] Loading configuration
[fastlane] Running build lane
[fastlane] Step failed: archive
[fastlane] Preserve the complete log and exit codeInsufficient disk space can cause cache, dependency extraction, and archive failures; an inconsistent toolchain can compound signing issues. Follow the sequence below strictly.
Run df -h Check the actual free space on the system and working volumes, then inspect DerivedData, archives, package manager caches, and old build artifacts.
Confirm that the project’s signing identity, provisioning profile, Bundle Identifier, and build configuration match. Do not only check whether the certificate file exists.
Result: the target configuration finds the matching signing identityCompare the execution users of the interactive session and automation process. Confirm that the task can read the required signing materials and record the stage at which the permission failure occurs.
Result: the automation user can read the required itemsKeep the lock file and failure logs first, then clear the relevant cache with the project’s tool. Do not delete all caches at once, or you will not be able to identify the source of corruption.
Result: dependency resolution is reproducible and versions are consistentRecord xcodebuild -version and xcode-select -p, then confirm that the version used by command-line tasks matches the project requirements.
Cleaning DerivedData, dependency caches, or archive directories changes the evidence. When submitting a ticket, include the error before cleaning, the cleanup action, and the result afterward.
An abnormal remote display does not necessarily mean the node is offline. First check whether command-line access works, then inspect client compatibility and display settings, and finally handle session reconnection.
| Observed symptom | Check first | Validation result |
|---|---|---|
| The client cannot establish a session | Check the node address, client version, network egress restrictions, and the delivered remote access method | The same node connects through a supported method |
| Intermittent lag or input delay | Record the local network type, time of the jitter, whether a proxy is used, and the transfer task running at the time | After reducing concurrent transfers, you can determine whether the issue is on the local link |
| Abnormal resolution or scaling | Check the client scaling policy, target resolution, and display settings within the session | Text and interactive areas display fully without being clipped |
| Keyboard shortcuts do not behave as expected | Confirm the local keyboard layout, modifier-key mapping, and client shortcut interception settings | Common key combinations produce consistent output in a test editor |
| The old screen remains after reconnecting | Check whether the old session is still running, record command-line reachability, and establish a new client session | The new session shows the current system state and responds to input |
| The session remains open after work is complete | Save your work, stop sensitive processes, lock the screen, and exit safely from the client | The session closes, and subsequent access requires verification again |
Client name and version, local network type, node, time of occurrence, display symptoms, command-line reachability, and the reconnection steps already attempted.
Do not submit passwords, private key contents, access tokens, or unsanitized signing materials. When describing a credential issue, state only the error type and the stage where it occurred.
SetMini targets 99.9% uptime. Nodes operate continuously 365 days a year; actual incident records and node status are based on the console response.
Determine eligibility using the service terms, including the measurement scope, excluded events, and claim requirements. Do not count issues with the user’s own network, credentials, or actions as node downtime.
Check node events against the ticket time.
Use it to identify recurring incidents of the same type.
The console record determines the status conclusion.
The claim should include the order number, node, incident start and end times, scope of impact, and related ticket records. Review and processing follow the service terms.
All orders are billed in USD. The available payment gateways and order status are determined in real time by the console. Include the order number when submitting a billing ticket.
The renewal amount depends on the selected model, rental period, node, and add-ons. Do not simply multiply the daily rate for another period; each of the four periods has its own listed price.
View full pricingPayment status, available gateways, and the amount due are determined in real time by the console.
| Add-on | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| +1TB SSD | $2.4 | $6.4 | $11.8 | $32.1 |
| +2TB SSD | $4.8 | $12.8 | $23.6 | $64.2 |
| Thunderbolt 5 daisy chain, per Mac | $1.5 | $4.1 | $7.6 | $20.7 |
For existing orders, submit through a console ticket first; the system will link your account and order context. If you cannot sign in to the console, email support@setmini.com.
Used to confirm the model, rental period, and add-ons.
Enter the region code and host identifier.
Include the time zone and the start and end range.
Attach the complete command, exit code, and key logs.
Describe each change and its result in order.
SetMini offers two tiers of dedicated Apple Silicon physical nodes, available for daily, weekly, monthly, or quarterly rental. Before ordering, compare the specifications, pricing, nodes, and add-ons.