Connection & Build Support

Capture the facts first,
then fix the cloud Mac issue.

Practical guidance for first-time connections, VNC sessions, Xcode builds, and order issues. Check your local network, node status, connection details, client, and task logs layer by layer instead of relying on blind retries.

Rent a Mac mini View desktop connection guide

Available nodes: 6 regions
Available configurations: 2 physical machines
Key details: Region, time, error text

CASE ROUTING / BAMINI

Issue triage record

Ready to submit

01 / CONTEXT Order & node Confirm the model, region, and current node status

02 / ACCESS Connection & credentials Check the address, account name, and client version

03 / EVIDENCE Logs & timing Keep the complete error text and time of failure

04 / ROUTE Self-check or ticket Reproducible issues enter the console ticket workflow

Choose an issue

Choose the closest match

All six entry points are visible at once. Choosing one takes you to the relevant checks without hiding the other guides.

Connection

Unable to establish a desktop session

Start by checking the local network, target address, client version, and session usage.

Troubleshoot connection Credentials

Connection details do not work

Confirm that the address, account name, and credentials belong to the same order, and avoid copying extra spaces.

Check the first-use path Performance

Screen, input, or tasks feel slow

Record network latency, desktop quality settings, and task resource behavior separately instead of treating them as one conclusion.

Review the observation order Orders

Order or billing needs review

Prepare the order number, billing period, USD amount, and payment result before submitting a console ticket.

View human support process Storage

Additional storage is not working as expected

Record the selected add-on, system detection result, mount path, and when the issue first appeared.

Prepare request details Builds

Xcode or runner task failed

Keep the version, label, working directory, complete log, and minimal reproduction steps.

Troubleshoot the build

First-use path

From node availability to desktop verification

Each step has a clear confirmation result. If a step fails, preserve the current state before changing anything else.

Check node status

About 30 seconds

Sign in to the console, open the relevant order, confirm that the node is connectable, and verify that its region matches your purchase selection.

Correct order number
Model and region match
Node is available

Get connection details

About 30 seconds

Copy the server address, account name, and connection credentials separately. Do not save them as combined fields or share them in public documents or chats.

No extra spaces in the address
Account name kept separate
Credentials belong to the current order

Establish a VNC session

About 1 minute

Enter the target address and account name in a trusted VNC client. Establish the session with the default quality first, then adjust resolution and color quality for your network.

Supported client version
Local network permits the connection
Error text preserved in full

Complete the first desktop check

About 2 minutes

After entering the macOS graphical interface, confirm that keyboard input, display scaling, Terminal access, and project directory access work normally before syncing the project or starting the runner.

Input and display work normally
Terminal commands run successfully
Project directory is readable and writable

Connection troubleshooting order

Verify one connection layer at a time

First determine whether the issue is local, related to target details, credentials, the client, or an existing session. Recording each result is easier to diagnose than repeatedly reconnecting.

VNC connection issue checklist
Order	Check	Action	Record	Pass criteria
01	Local network	Switch to a known-stable network and confirm that a firewall or proxy is not blocking the VNC connection.	Network type, proxy usage, failure time	The target address is reachable on the same network
02	Target address	Copy the server address again from the current order. Do not use an old screenshot or an address saved for another order.	Order number, node region, address source	Address matches the current node record
03	Connection credentials	Check the account name and credentials separately, including whether copied text has spaces or line breaks at either end.	Error text; never submit the actual password	The client no longer returns an authentication error
04	Client version	Record the client name, version, and display settings. If needed, cross-check with another trusted client.	Client version, OS version, quality settings	The same details establish a stable session
05	Session status	Check for an existing session, a frozen screen, or an invalid connection still retained by the client.	Actions before disconnect, reconnect behavior, session time	Reconnect works after closing the old session

Break performance issues into separate signals

Input latency, slow screen refresh, and build duration are three different metrics. Record network conditions, VNC quality settings, and task logs separately instead of attributing every symptom to node performance.

Build troubleshooting

Separate project configuration from node environment

Save the failure state first, then create a minimal reproduction. The following six items should come from the same failed task; do not mix logs from different times.

BUILD / VERSION

Xcode and tool versions

Record the full Xcode version, command-line tools selection, and the build command actually used by the task.

Focus Can the same project fail repeatedly on a fixed version?

BUILD / LOG

Complete project log

Keep the context before and after the failed step, not just the final error line.

Focus Did the error occur during dependency, compilation, testing, export, or script execution?

BUILD / TIME

Time of failure

Record the time zone, start time, failure time, and task duration so they can be matched to node records.

Focus Does the issue occur at a fixed step or after a fixed duration?

RUNNER / LABEL

Runner label and directories

Confirm that the workflow matches the expected label, and record the working directory, cache directory, and execution account.

Focus Was the task routed to the correct self-hosted runner?

REPRO / STEPS

Minimal reproduction steps

Remove unrelated scripts and parallel tasks, then reproduce the same error with the fewest commands possible.

Focus Does the failure depend on the current project configuration, cache, or environment variables?

COMPARE / RESULT

Comparison result

Retest on the same node with a clean working directory, or run a minimal example with the same toolchain.

Focus If the minimal example also fails, submit a ticket as a node environment issue.

Project configuration signal

Only a specific branch, dependency, cache, or script fails, while a clean example runs.

Node environment signal

Multiple independent projects fail at the same tool step, and the minimal example reproduces the issue consistently.

Technical glossary

Use consistent technical terms in tickets

Clear terminology reduces back-and-forth caused by mixing up machine, instance, and server.

Physical node: The physical Mac mini hosting macOS and development tasks. Node status, region, and connection details are tied to a specific order.
Dedicated physical machine: A physical device resource dedicated to one order, with no shared operating system environment with other customers.
Non-virtual machine: A macOS environment delivered on physical hardware, not a virtual instance carved out of a shared host.
VNC: A connection method for viewing and controlling a remote graphical desktop. Quality, scaling, and input latency depend on local network and client settings.
Self-hosted runner: An automated task executor deployed on the rented cloud Mac and registered and maintained by your team.
Billing period: The day, week, month, or quarter selected for the order. When checking a bill, provide the model, period, and add-ons as well.
Node region: The service region where the device is located. BAMini offers 6 nodes: Singapore, Tokyo, South Korea, Hong Kong, US East, and US West.
Thunderbolt 5 daisy chaining: Additional connection capability selected per device. For related issues, specify the number of devices and the connection topology.

Prepare before submitting

Make the request reproducible and verifiable

A processable request needs order context, timing, the complete error, and steps already tried. Sensitive credentials are not troubleshooting materials.

SUPPORT REQUEST / REQUIRED FIELDS

Issue evidence checklist

7 items

01 Order number

Used to locate the order record; do not provide only the model name.

02 Node region

Specify Singapore, Tokyo, South Korea, Hong Kong, US East, or US West.

03 Available model

Enter BookAMini M4 Core or BookAMini M4 Plus.

04 Time of occurrence

Include the date, time, and time zone so it can be matched to node records.

05 Complete error text

Copy the original text, including the error code and context; do not merely say “it does not work.”

06 Steps already tried

List them in execution order and state the result of each step.

07 Reproducibility

State whether it happens every time, intermittently, or only with a specific project or network.

Escalate to human support

When self-checks cannot close the loop, submit a console ticket

For existing orders, use a console ticket first so the order, node, and follow-up records can be linked. If you cannot sign in to the console, use the support email.

01 / RECEIVE

Submit the issue and evidence

Create a ticket in the console, select the relevant order, and attach the region, model, time, error text, log excerpts, and reproduction steps.

02 / CLASSIFY

Separate connection, environment, or billing

Support staff will determine the scope from the evidence. If information is missing, the ticket will list the exact fields to add.

03 / FOLLOW UP

Reply in the original ticket

When adding new logs, include the new occurrence time and test conditions. Do not create multiple tickets for the same issue.

04 / RESOLVE

Review the conclusion and next steps

Check progress, recommended actions, and required verification results in the console. After verification, confirm recovery in the original record.

TICKET

Existing order or node issue

Open a console ticket and link the relevant order.

Open console

Unable to sign in to the console

Email from the account address and provide the order number and details of the sign-in issue.

support@bookamini.com

Ready to start building

Choose from 6 nodes and two dedicated physical machines.

BookAMini M4 Core and BookAMini M4 Plus are dedicated physical cloud Macs, not virtual machines. Orders are billed in USD; availability is based on the console’s real-time status.

Rent a Mac mini View configurations and pricing