First, check in the portal that your instance is ready. Then connect to your dedicated physical Mac mini. Build from the command line, inspect the environment in the remote desktop, and let CI handle repeatable tasks.
Already have an instance? Check its connection details. If you haven't rented one yet, start with an order. Connection credentials are never displayed on public pages.
Open the instance details in the portal and check the instance ID, node, and status. Use the public address, username, port, and initial credentials returned for that instance. Don't reuse connection details from another machine.
Use SSH to run build commands, transfer files, and inspect logs. The default SSH port is 22. If your instance uses a different port, use the value shown in its details.
Get the host address and username from the instance details. On your first connection, verify the host fingerprint before adding your public key. Keep your private key on your device; never include it in a support ticket.
See a first-build exampleUse VNC to open Xcode, check the Simulator, and adjust settings in the graphical interface. The default VNC port is 5900. Find the connection address, password, and actual port in the instance details.
Once connected, check that the desktop responds. Don't reuse your VNC password in a code repository. Where supported, connect through a controlled access path or an SSH tunnel.
Troubleshoot desktop accessLog in to the portal and open the connection option shown in your instance details. If a web terminal is available, connect over HTTPS in your browser. It usually uses 443, so you don't need to enter a separate terminal port.
Access is tied to your logged-in account session; it's not a public link. If the option isn't shown for your instance, use SSH or VNC instead. Don't guess the terminal address.
View instance connection optionsFirst confirm that you can log in, then check the Xcode path and version. The output below is an example, not a live instance log. Session names, build numbers, and timings are included only to show where to look.
$ ssh -p <SSH_PORT> <USER>@<HOST>
Welcome to MergeMac
$ xcode-select -p
/Applications/Xcode.app/Contents/Developer
$ xcodebuild -version
$ cd <PROJECT_DIRECTORY>
$ xcodebuild -scheme App archive
** ARCHIVE SUCCEEDED **
$ fastlane pilot upload
Successfully uploaded Build 214Replace the values in angle brackets with the details for your instance. App is an example scheme. For a workspace project, pass your own -workspace and make sure the scheme is shared.
Uploading also requires valid signing, an export configuration, and upload credentials. This example assumes fastlane is configured for the project. Build 214 isn't proof of your delivery; rely on the output from your upload tool.
MergeMac provides a dedicated physical node. You manage your CI repository permissions, job configuration, and credentials. First run the archive successfully in a terminal as the same user your runner will use. Then register the runner, so environment issues aren't mistaken for scheduling issues.
mergemac, macos, and m4. Use runs-on in your workflow to match them.Don't let untrusted external pull requests run directly on a runner that has access to signing materials. Authorize release jobs separately from routine checks.
macos and xcode, and declare them explicitly in your jobs. Restrict release runners to protected branches or tags.Revoke the runner's authorization in your CI platform when rotating its token or ending the rental. Deleting files from the node won't revoke platform access.
These terms describe resources and connection methods. They don't include extra software licenses or combine multiple machines into one larger Mac.
Record the time and time zone, instance ID, full error, and most recent change. Change one thing at a time, then repeat the same check. Reinstalling should not be your first step.
First check that the instance is ready in the portal, then test the SSH connection. If SSH works but the desktop doesn't, check whether a user is logging in, logging out, or switching graphical sessions. Quit the client and reconnect.
If the screen is still black, note the client version and save a screenshot, then open a support ticket. Don't disable the firewall or repeatedly force-restart the machine to troubleshoot; doing so could interrupt a running build.
Run xcode-select -p and xcodebuild -version. Check both your interactive session and the runner. Having multiple versions installed doesn't mean the command line is using the one you expect.
For a single job, set DEVELOPER_DIR to the target Xcode Developer directory instead of changing the machine-wide default and affecting other jobs. If the directory doesn't exist, check the installation path rather than copying an example path.
Check available space with df -h, then inspect DerivedData, archives, device data, and simulator runtimes. Export any build artifacts you need to keep and stop jobs that are using simulators.
xcrun simctl delete unavailable removes records for unavailable simulator devices; it doesn't remove every runtime. Check what you're deleting first. Don't recursively delete project directories or Keychains.
Work out whether the certificate has expired, the provisioning profile is invalid, the private key is missing, or the Keychain is locked. Check the certificate's validity period, team, and bundle identifier, then confirm that the CI user can access the corresponding private key.
After renewing a certificate, update the provisioning profile and protected variables, then test again with the same scheme. Include only error codes and redacted logs in your ticket; never send private keys, certificate export passwords, or complete signing materials.
Reinstalling the system and clearing data after a rental ends are separate processes. Don't use your rented node as the only place to store source code, signing materials, or build artifacts.
Open your instance details in the portal. Before reinstalling the system, stop CI jobs, export your projects, artifacts, and required configuration, and make sure you can open the backup somewhere else.
Initialization usually takes a few minutes. Check the portal for the actual status and completion time. Don't submit the task repeatedly while it's running. Once it's complete, retrieve your connection credentials again, verify the host fingerprint, and rebuild your development environment.
After reinstalling, verify SSH, Xcode, dependencies, and your runner again. Don't assume the previous service configuration is still there.
After your rental ends, the node goes through data cleanup and a system reset before it's prepared for another customer. Export anything you need to keep before the end of your rental; don't rely on being able to connect afterward as a backup plan.
Also revoke repository deploy keys, CI runner tokens, and upload credentials. Disk erasure removes data from the node, but it doesn't revoke access to external systems on your behalf.
For questions about data handling or security boundaries, review the security information first, then ask about your specific instance in a portal ticket.
For issues with a rented instance, submit a portal ticket so we can link it to your order and node. If you can't log in, have a pre-sales question, or need to report a security issue, email our support team. Please don't open multiple tickets about the same issue.
Log in and open the support area. Include your instance ID, the impact, and steps to reproduce the issue. To escalate an existing issue, add details to the original ticket so troubleshooting stays in one thread.
Suggested format: time and time zone → expected result → actual error → steps already tried. Attach the shortest relevant redacted log excerpt; don't upload your entire source tree.
Log in and submit a ticketIf you can't access your account, explain the issue in the subject line and include your registered email address and an order number we can use to verify your account. Never send your account password or payment card number.
Our team works across Asia-Pacific and US Eastern time zones. Response times depend on the issue's priority and the current queue. We'll share updates by ticket or email; we don't promise an unpublished average response time here.
support@mergemac.comAlready have a machine? Check its status in the portal. Need another build node? Choose a rental plan. Every machine is a dedicated physical Mac mini, not a virtual machine.