Find the issue. Get your build back on track.

After your payment is confirmed, sign in to the portal, open the relevant order and view its host details to find the IP address, username and initial password. Before connecting, check that the configuration, host and rental term match your order. The portal shows the latest delivery status.

1. 01Check your order

   Note the order number, configuration and host ID so you don't use credentials for another host.

2. 02Copy your credentials

   Copy the full IP address and username, and check for accidental spaces. Don't paste your initial password into public logs.

3. 03Change your password

   Once you're signed in, change the current user's password and save it in your password manager.

ssh -p 22 USER@NODE_IP
passwd

Replace USER and NODE_IP with the values shown in the portal. If the details show a different port, use that port. It's normal for password characters not to appear as you type them in SSH.

First, distinguish between a payment being initiated and the platform confirming receipt. A completed card payment page or a submitted on-chain transfer doesn't replace the payment status shown in your order. Refresh the order and check the amount and transaction status. Don't pay again just because the page hasn't updated yet.

If the payment record and order status don't match, submit a portal ticket with your order number, payment method, amount, payment time and time zone. For USDT-TRC20, include the transaction hash. For card payments, the reference details from your receipt are enough. Don't share your full card number, security code or SMS verification code.

Arm Line M4 comes with M4 / 16GB / 256GB; Arm Grid M4 Pro comes with M4 Pro / 64GB / 2TB. Both configurations are available across these 5 locations: Singapore, Tokyo, Seoul, Hong Kong and the US East Coast. Check the portal for current availability.

For interactive work, consider the network path between your team and the host. For unattended builds, also consider the transfer path for code, dependencies and build artifacts. If your order doesn't match your expectations, check it in a support ticket before uploading project or signing materials.

Disconnect any duplicate remote sessions, then reconnect. Check that your client is connecting to the current host and that macOS isn't at the Lock Screen or user-switching screen. If SSH still works, save your build logs. Don't force-restart a host while an archive is running.

If you can access the desktop, check Screen Sharing and the list of allowed users under “System Settings → General → Sharing”. The exact location may differ slightly between macOS versions. You can check the current console user over SSH to see whether a graphical session is active:

stat -f '%Su' /dev/console

If the screen stays blank, note whether SSH is reachable, what you were doing beforehand, and your client name and version in a ticket. Attach a screenshot without passwords. Don't repeatedly terminate system processes as a troubleshooting step.

Set the VNC client's display mode to “Fit to window” first, so you can tell client-side scaling from the remote display's actual resolution. On the host, check the current display options under “System Settings → Displays”. Start with 1920 × 1080, then adjust based on your screen and network.

For connections across regions, try a lower resolution and colour depth with a higher compression level. Check that text input and menus feel responsive before increasing image quality. Build jobs don't depend on remote desktop quality, so you don't need to keep a high-resolution graphical session open just to monitor logs.

A timeout usually means the network path or port isn't responding. A connection refusal means the host responded but rejected the connection, so check the port and service. For authentication failures, check the username, password or key. Start in your local terminal, then attach relevant log excerpts to a ticket:

nc -vz NODE_IP 22
ssh -vv -o ConnectTimeout=10 -p 22 USER@NODE_IP

If your company network restricts outbound connections, try another network and record both results. Keep the error lines in your logs, but hide your public IP address, username, private key path and other sensitive information. Never send your private key to support.

The host fingerprint may change after a full system reinstall. Verify the host identity in the portal first; don't ignore a host key warning until you've confirmed the identity.

On the remote host, check the input source under “System Settings → Keyboard → Text Input”, then check the Command, Option and Control mappings under “Modifier Keys”. Modifier keys are in different places on Windows and Mac keyboards. Test symbols in a plain text editor before entering terminal commands.

If the issue only occurs in your remote client, check its keyboard layout and shortcut forwarding settings. If clipboard sync isn't working, reconnect and check the client's clipboard sharing option. Don't use a public clipboard service to transfer passwords or signing materials.

Check the active developer directory and Xcode version first. Opening a particular Xcode in the GUI doesn't mean the command line is using the same version. Changing the global selection affects jobs on the same host; for shared build pipelines, set DEVELOPER_DIR for an individual job instead.

xcode-select -p
xcodebuild -version
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer \
  xcodebuild -version

The path must point to an Xcode installation that exists on the host. Before changing the global selection, pause jobs that depend on the current toolchain, then run sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer. Check any first-use component and licence requirements in an interactive session first.

Check the runner's execution user and the Keychain that contains the certificate. A logged-in GUI session doesn't necessarily carry over to a background service. After a restart, you may also need to unlock a dedicated build Keychain according to your pipeline's policies. Use these commands to check signing identities and unlock a Keychain interactively:

security find-identity -v -p codesigning
security unlock-keychain "$HOME/Library/Keychains/build.keychain-db"

The build Keychain in this example must already exist. For unattended jobs, read required credentials from CI secret variables, disable command echoing and limit certificate access. When troubleshooting, share only the error code and redacted logs. Don't send Keychain passwords, private keys or certificate export passwords.

Start with the signing approach already validated by your project. Automatic signing suits workflows with controlled authorisation for automation. A manual profile suits release pipelines that need fixed certificates, provisioning profiles and export settings. Don't change your signing strategy and Xcode version during the same troubleshooting run.

For manual signing, check the Bundle Identifier, Team ID, certificate expiry, profile type and export method. For projects with multiple targets, check extension identifiers and entitlements as well. Track build failures separately from export failures, and include the failing stage, original error and a redacted export configuration in your ticket.

First, check on your source control platform that the runner registration is still valid. Then check the service status, repository binding and job labels on the host. Run the following GitHub Actions commands from the runner installation directory. GitLab Runner commands require the relevant program to be installed:

./svc.sh status
gitlab-runner status
launchctl list | grep -i runner

For a service managed by launchd, check the execution user, working directory and log path in its service definition. Starting at boot and starting after a user logs in are different behaviours. After configuring the service, test it without an interactive terminal. Don't paste runner registration tokens into a support ticket.

Print non-sensitive environment details from the failing job and check the actual execution user, working directory, PATH and Xcode version. Background services don't necessarily load all of your interactive shell configuration.

whoami
pwd
printf '%s\n' "$PATH"
xcodebuild -version

Set dependency paths explicitly in the job environment. Give concurrent jobs separate paths for their workspaces, DerivedData, archives and temporary files. Get one clean build working before gradually increasing concurrency. Don't let two releases modify the same export directory or signing resources at the same time.

Be sure to select TRC20. Carefully check the payment address, amount due and payment instructions for your current order. Don't reuse an address from another order or an old screenshot. Before sending, make sure your wallet is set to the right network.

On-chain confirmation usually takes minutes, so allow a few minutes to check the transaction status. The actual time depends on network congestion, wallet broadcast and the number of confirmations required by the payment gateway; it isn't a guaranteed settlement time. Use the confirmation status shown in your order. Submitting a transfer doesn't mean the platform has confirmed receipt.

If the transaction is confirmed but your order hasn't updated, submit your order number, transaction hash, transfer amount, time and time zone. Don't send the payment again, and never share your wallet recovery phrase or private key in a ticket.

Visa / Mastercard / Amex payments are processed through Stripe. After paying, return to the portal and check the status of the relevant bill and the amount in USD. If your bank shows a transaction but the bill status doesn't match, keep the receipt and submit a ticket. Don't repeatedly submit the payment.

Include your order number, payment time and time zone, amount, failure message or payment reference number. Redact your full card number, security code and other personal information in screenshots. Support will never need your SMS verification code.

Rentals are available for four terms: daily, weekly, monthly and quarterly. Check the relevant order and bill in the portal for the start date, end date, renewal action and order status. Don't estimate your service end time based on when you initiated a transfer locally.

Before your rental ends, check the renewal status and outstanding bill in your order. Don't assume your service will continue without payment. Pausing a runner or disconnecting SSH doesn't end your rental. If you need to change your setup, confirm the options in a ticket first, then plan your project migration and pause builds as needed.

All data on the host is erased after the rental ends. Before then, move your source code, build artifacts, essential logs and configuration backups, and check that your backups can be restored. Don't rely on the host's disk as your only copy.

Also unregister the runner, revoke any automation tokens used on the host and handle signing materials according to your security policies. If you're moving to another host, verify the new host before switching your release jobs.