Troubleshoot setup, connections, development toolchains, storage, and billing by task. Each guide provides a verification order, commands, and diagnostic details to retain for HireAMac dedicated Apple Silicon physical nodes.
Search terms include connection timeout, credentials, Xcode, Swift, CI Runner, SSD, and order periods. Search only filters this page and does not upload your input.
6 help topics currently shown.
Confirm the node and access requirements first, then verify the system and build tools. Do not change credentials, the client, and the toolchain at the same time while the connection is still unstable.
Open the instance details for the order and record the model, region, connection address, and current session status. The three available configurations are HireAMac M4 S (M4, 16GB, 256GB), HireAMac M4 M (M4, 24GB, 512GB), and HireAMac M4 Pro L (M4 Pro, 64GB, 2TB). The region must be Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or the US East.
Use the console-provided method to create strong credentials, and store them in a controlled password manager or secrets store. For the first connection, verify login only—do not rush to upload a project, install dependencies, or start a long-running task. For team access, grant the minimum permissions required and revoke access promptly when a member leaves the project.
Once the graphical desktop opens normally, run the following read-only commands in Terminal. Retain the text output; there is no need to capture the entire desktop, including sensitive paths or credentials.
sw_vers
uname -m
xcode-select -p
xcrun swift --version
xcodebuild -versionThe expected architecture is arm64. If xcode-select -p does not return a valid developer directory, configure the command-line tools path before continuing build verification.
Choose a small project without production credentials, resolve dependencies first, and then run a clean build. Check the exit code, artifact directory, remaining disk space, and build log. Once the minimal task succeeds, migrate larger repositories, caches, and automation workflows so environment issues can be separated from project issues.
df -h /
xcodebuild -project Sample.xcodeproj -scheme Sample -showBuildSettings
xcodebuild -project Sample.xcodeproj -scheme Sample clean buildThe order matters. Prove that the route is reachable before addressing authentication and client display issues, so network failures are not mistaken for credential errors.
Confirm that the local network has no proxy rules, corporate firewall, or temporary-hotspot restrictions. Retest on the current network and another trusted network, and record whether only one route fails.
Verification points DNS resolution, route reachability, port policy, packet lossReturn to the console to verify the instance address, region, and status. Avoid using an address saved by an old session. Teams working across regions should confirm that members connect to the physical node associated with the same order.
Verification points Order ID, node region, connection address, status update timeCheck the username, key-file permissions, and the most recent credential rotation. When authentication fails, do not repeatedly try unknown credentials; first confirm the single trusted source.
Verification points Username, key permissions, credential version, original authentication errorConfirm that there is no leftover full-screen session, open remote desktop, or running automation task. Safely exit the old connection before creating a new session; do not force-terminate a process that is writing data.
Verification points Existing sessions, active processes, desktop lock, last disconnect timeCheck the client version, resolution, color settings, and clipboard policy. If the terminal is reachable but the graphical desktop is not working, the issue is usually narrowed to the session or client layer.
Verification points Client version, display settings, input method, file-transfer policyInclude the time zone with the timestamp. Keep only the necessary lines around the error, and replace usernames, private paths, tokens, keys, and project secrets.
Issue type:
Order ID:
Model:
Node region:
Time and time zone:
Local network type:
Connection method and client version:
Original error message:
First occurrence or reproducible:
Checks completed:
Redacted log excerpt:A tool being present does not mean the task is usable. During verification, record the executable path, actual version, selected developer directory, and the minimal task exit code.
First read the Xcode version and current developer directory, then use xcrun to verify tool resolution. After switching between versions, reopen Terminal and run the build task as the same user to prevent interactive and automated sessions from using different paths.
xcodebuild -version
xcode-select -p
xcrun --find xcodebuild
xcrun simctl list runtimesCheck the Swift compiler, system architecture, and core build tools separately. If the interactive terminal succeeds but the automated task fails, compare their PATH, working directory, user identity, and environment variables instead of reinstalling tools immediately.
xcrun swift --version
clang --version
uname -m
pwd
printf '%s\n' "$PATH"Transfer certificate files through controlled paths, restrict file permissions, and verify their purpose and validity before importing them. During diagnosis, record only the filename, purpose, permissions, and verification result. Never send passwords, private keys, or valid access tokens in screenshots, build logs, or ticket attachments.
ls -l /path/to/certificate
file /path/to/certificate
security find-identity -v -p codesigningRegardless of the repository platform, verify the Runner process user, working directory, available disk space, toolchain path, and task exit code. Run a probe task that does not access production resources before connecting the full pipeline. Failed logs should include the stage name and command result.
whoami
pwd
df -h /
xcode-select -p
xcodebuild -version
xcrun swift --versionAccount for the combined usage of source code, dependency caches, build intermediates, archived artifacts, experimental data, and export copies, while keeping free space available for cleanup.
Best for workflows with predictable capacity needs, repeatable dependency downloads, and timely artifact exports. Large simulator runtimes, archives, and caches can far exceed the source itself; size for peak usage rather than initial consumption.
Suitable for parallel branches, retained dependency caches, or steadily growing build artifacts. Before ordering, confirm that the added capacity covers the period when the working set and export copies coexist.
Suitable for high-capacity experimental data, multiple large projects, or tasks that retain many intermediate artifacts. Capacity expansion does not replace a backup strategy; export and verify critical data independently before the rental period ends.
Upload the smallest runnable set first, verify permissions, file integrity, and directory structure, then upload large assets in batches. Do not include keys in repository archives or general data packages.
Record the source path, destination path, file count, and verification result. Pause tasks that continuously rewrite the same directory during migration to prevent inconsistent source and destination states.
Delete regenerable caches and temporary artifacts first. Confirm that active tasks are not using the target directory before cleanup, and retain records of the deletion scope and released capacity.
Before the rental period ends, export source code, configuration, artifacts, and necessary logs, then verify file counts or checksums. Confirm that external copies open correctly before handling working data on the node.
df -h /
du -sh ~/Projects
du -sh ~/Library/Developer/Xcode/DerivedData
find ~/Projects -type f | wc -lAll orders are billed in US dollars (USD). Available payment gateways are confirmed in real time by the console and include USDT-TRC20 and Visa / Mastercard / Amex (via Stripe).
| Model | Configuration | Per day | Per week | Per month | Per quarter |
|---|---|---|---|---|---|
| HireAMac M4 S | M4 / 16GB / 256GB | $20.9 | $56.4 | $104.4 | $284 |
| HireAMac M4 M | M4 / 24GB / 512GB | $41.2 | $111.2 | $205.9 | $560 |
| HireAMac M4 Pro L | M4 Pro / 64GB / 2TB | $59.9 | $161.8 | $299.6 | $814.9 |
| Add-on | Per day | Per week | Per month | Per quarter |
|---|---|---|---|---|
| +1TB SSD | $2.9 | $7.7 | $14.3 | $38.9 |
| +2TB SSD | $5.8 | $15.4 | $28.6 | $77.8 |
| Thunderbolt 5 parallel connection (per node) | $1.3 | $3.6 | $6.7 | $18.2 |
Best for temporary builds, bug reproduction, and short task validation. Check the order's number of days, daily model price, daily add-on prices, and node field.
Best for release sprints or continuous testing. The bill should show the selected model's weekly price and any storage or parallel-connection add-ons billed weekly.
Best for day-to-day development and stable CI workflows. Check the monthly period boundaries, model price, node, and monthly charge for each add-on.
Best for ongoing tasks with stable requirements. Confirm that the model price, add-on prices, and order period all use the same billing cycle.
You can submit a ticket through the console or email support@hireamac.com. Do not send access keys, passwords, valid tokens, or unredacted project data.
Specify Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or the US East, along with the corresponding available HireAMac model name.
Provide the order ID shown in the console. The occurrence time must include the date, time, and time zone; for recurring issues, provide the start and end range.
Start from a known-good state and list each action, input, expected result, and actual result. Note whether the issue occurs every time.
Retain the original error, command exit code, and necessary context. Replace usernames, private paths, keys, tokens, certificate contents, and business data.
Need a new node? Compare the three configurations and four rental periods. For an existing instance issue, sign in to the console and submit a ticket with your diagnostic results.