You’re connecting to a dedicated cloud-based physical Mac, not a virtual machine. First, check your order and delivery details in the console, then open the desktop using the connection method provided. Use the connection settings listed in your delivery details.
Already have an order? Find your instance details in the console. Don’t use connection settings from another order.
This checklist is a reference, not actual connection credentials. Use the console delivery details for the specific address, method, and settings.
Check your order, network, and local device separately to avoid mistaking the wrong node for a connection issue.
Find the instance you want to connect to in the console and check the node selected for your order. Available regions include Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West. Use the region specified in your order.
Make sure you can sign in to your console and view the delivery details for the relevant instance. Console account details and remote session credentials are separate—don’t confuse the two.
Check that your device is online, your connection is stable, and your network allows remote connections. If you switch networks, test the connection again before drawing conclusions.
Install a remote desktop client that supports the connection method in your delivery details. Use the client type and settings specified there; don’t assume a port or protocol.
Verify one thing at each step. If a setting doesn’t match, check the instance details again instead of guessing the default.
Sign in to the console and find your ordered physical Mac. Note the connection method and settings provided for that instance, then confirm its node and model.
Enter the connection settings from your delivery details in a compatible client. Use credentials only on trusted devices, and never post the full settings in a public repository or forum.
Once connected, make sure the desktop is visible and test your mouse, keyboard, and window controls. Before starting development, check that the required toolchain and project files are ready.
VNC is a technology for transmitting and controlling a remote graphical desktop. It describes a connection method, not a universal set of addresses, ports, or default credentials. Check your instance’s delivery details to see which clients you can use and which settings to enter.
A successful connection doesn’t mean your development environment is ready. Before opening your project, check its macOS and Xcode requirements, dependencies, and the access permissions needed for certificates and provisioning profiles.
Check your local setup first, then compare it with your delivery details. Support teams can help more quickly when you describe a reproducible issue rather than just saying “I can’t connect.”
| Check | What to verify | What to note |
|---|---|---|
| Local network | Is your network working? Does the issue change when you switch networks? | Where does the connection attempt stop? Does it time out? |
| Client settings | Does your client support the connection method? Do the entered settings match your delivery details? | What error does the client show, and at what point does it appear? |
| Session status | Can you view the relevant instance details in the console? | Can you see the desktop? Do mouse and keyboard inputs work? |
| Selected node | Are you connecting to the physical node selected for your order? | Order model, node, and when the issue occurred. |
If you still can’t identify the issue, sign in to the console and submit a support ticket. Include the error message, steps you’ve tried, and how to reproduce the issue. Never include passwords, tokens, or private keys.
When you’re done, end the remote session and make sure no reusable connection details remain on shared devices. Store credentials in a team-approved secure location—not in project code or build logs.
If you used this Mac to handle development certificates, provisioning profiles, or signing keys, check where they’re stored and who can access them before you leave. When handing work over, clarify who is responsible for them. Never send sensitive information in a support ticket.
Make sure this device is no longer connected to the desktop.
Check the client’s saved settings and any records on shared devices.
Review where certificates, keys, and project files are stored.
Remote desktop gives you access. Choosing the right setup for parallel development tools, project caches, and build tasks also depends on your Mac’s specifications.
Choose a model, node, and billing period. Once your order is complete, connect to the desktop using the delivery details in the console.