guides://search — Support Center

Hit a snag? Fix it here first.

> Type your issue, or start from the window below. Most problems are solved in under 5 minutes on your own.

No matching entries. Try a different keyword, or just email support@opsmac.com and paste the exact error message.

guides://quick-start

Quick Start: Five Guides From First Boot to CI Integration

Credentials land in your inbox about 4 minutes after payment. Work through the five guides below in order — from your first login to CI integration — without needing to contact anyone.

First Boot

What's in the credentials email, the first three things to do, and how to confirm your machine is ready.

See the steps →

Update Your Credentials

Change the initial password and VNC password right after your first login, then switch to key-based login.

See the steps →

First SSH Connection

Log in to your dedicated physical machine with a single command — fingerprint confirmation and passwordless setup.

See the steps →

VNC Remote Desktop

Open the macOS graphical desktop: enabling screen sharing, client settings, and resolution recommendations.

See the steps →

Set Up a Self-Hosted Runner

Route your CI build jobs to this machine in three steps: register, tag, and run as a persistent service.

See the steps →
guides://quick-start — 5 guides · expand to read
First Boot: Your First 5 Minutes After the Credentials Email

Once payment is confirmed, the system automatically provisions a dedicated physical Mac mini and initializes macOS. The credentials email usually arrives in about 4 minutes and includes: node IP, system account name, initial password, and VNC port. Do these three things in order:

  1. SSH in once using the IP and account from the email to confirm the machine is online and the account works (see "First SSH Connection" below for the command).
  2. Change the initial password and VNC password right away (see "Update Your Credentials") — the initial password is meant for one-time use only.
  3. Check the console to confirm the instance status shows "Running," and verify the node and model match your order.

The machine ships with Xcode and common command-line tools pre-installed. Both the macOS GUI and command line are fully usable right away — no extra activation steps needed.

Update Your Credentials: Replace the Initial Password With a Key
  1. After SSH login, run passwd and follow the prompts to enter your old and new passwords, changing the system account password.
  2. The VNC password is changed separately: on the graphical desktop, go to System Settings → General → Sharing → Screen Sharing, and update the access password in the options.
  3. Append your local public key to the machine's ~/.ssh/authorized_keys for passwordless login. Once the key works, we recommend disabling password login in sshd_config.
terminal — passwd
passwd
Changing password for opsmac.
Old Password: ********
New Password: ************
passwd: password updated successfully

This is a dedicated physical machine — credentials are issued to you and you alone. Safekeeping your credentials is your responsibility; if they're ever compromised, change your password immediately and open a ticket.

First SSH Connection: One Command to Log In to Your Mac
  1. Open a local terminal (on Windows, PowerShell or Windows Terminal both work) and run ssh account@node-ip.
  2. On first connection you'll be asked to confirm the host fingerprint — type yes and press Enter. The fingerprint is saved to your local known_hosts, so you won't be asked again.
  3. Enter the initial password from the email; once you see the shell prompt, you're logged in. Then follow "Update Your Credentials" to switch to key-based login.
terminal — ssh
ssh opsmac@203.0.113.24
The authenticity of host '203.0.113.24' can't be established.
Are you sure you want to continue connecting (yes/no)? yes
opsmac@mini-sg-01 ~ %

For full instructions on uploading keys, hardening security, and restricting by source IP, see the step-by-step guide on the "How Do I Connect" page →

VNC Remote Desktop: Opening the macOS GUI
  1. Screen sharing is enabled by default when your machine is delivered. If it's off, SSH in and re-enable it under System Settings → General → Sharing.
  2. Install any standard VNC client locally, enter node-ip:VNC-port as the address (the port is in your credentials email), and use your VNC password to connect.
  3. We recommend starting at 1920×1080 resolution with "medium" color quality. On cross-region connections, prioritize smoothness first, then dial up quality as needed.
  4. macOS users can also press ⌘K in Finder and enter vnc://node-ip to connect with the built-in Screen Sharing app.

The graphical desktop and command line work independently and at the same time: use VNC for Xcode's GUI, and SSH for build scripts — one doesn't interfere with the other.

Setting Up a Self-Hosted Runner: Three Steps to Join the CI Pool
  1. Create a new self-hosted runner in your repository settings on your code hosting platform to get a registration token.
  2. SSH into your cloud Mac, download the runner package, and run config.sh to register. We recommend designing labels around "OS + chip + purpose" so workflows can target the right machine precisely.
  3. Install it as a persistent service with svc.sh (backed by launchd) so the runner automatically comes back online after a reboot.
terminal — runner
./config.sh --url your-repo-url --token registration-token --labels macos,m4,selfhosted
./svc.sh install && ./svc.sh start
√ Connected to server. Listening for Jobs

Concurrency tip: the M4 Home (16GB) is most stable running a single concurrent job; for parallel workloads, choose the 64GB M4 Pro Workstation. For a deeper dive into service configuration, see the "How Do I Connect" page →

guides://glossary

Mini Glossary: 7 Terms to Understand Our Product Pages

Terms that keep showing up on our product pages and invoices, explained in two sentences each. Understand these and you're unlikely to pick the wrong plan.

glossary://terms — 7 entries
Physical Node node
A real, whole Mac mini sitting in a data center rack. What you rent is the machine itself — not a slice carved out of it.
Dedicated dedicated
For the duration of your lease, the entire machine's CPU, unified memory, SSD, and bandwidth belong to you alone — no noisy neighbors, and build times stay predictable.
Non-Virtualized non-virtualized
macOS runs directly on Apple Silicon hardware with no virtualization layer in between. There's zero performance overhead — Xcode build times are true bare-machine times.
VNC screen sharing
A graphical remote desktop protocol natively supported by macOS. Install any standard VNC client and control the whole desktop as if you were sitting right in front of it.
Self-Hosted Runner CI
A self-hosted CI executor. Once registered on your cloud Mac, build jobs from platforms like GitHub Actions get dispatched straight to your dedicated physical machine.
Unified Memory unified memory
Apple Silicon's CPU and GPU share the same high-bandwidth memory pool. The 64GB configuration can fit a medium-sized MLX inference model directly.
TestFlight beta distribution
Apple's official beta distribution tool. After building your app with fastlane on your cloud Mac, you can upload it straight to TestFlight for testers to install.
troubleshoot://checklist

Troubleshooting: Work the Checklist Before You Open a Ticket

The four most common issues, each with a step-by-step self-check list. In practice, about 80% of cases get resolved before reaching the last step.

troubleshoot://common — 4 common issues
Can't SSH In: Timeout or Connection Refused
  1. First, ping node-ip. All four nodes are online year-round, so if ping fails, it's most likely your local network or an egress restriction — try a different network.
  2. Test the port: nc -vz node-ip 22. If ping succeeds but the port doesn't respond, check whether you've changed the sshd port or firewall rules.
  3. Getting "Permission denied": double-check the account name spelling, verify your local private key permissions are set to chmod 600, and confirm the public key is still in the machine's authorized_keys.
  4. Check the instance status in the console. If it shows an issue, restart it directly from the console — it typically recovers within about a minute.
  5. If you've tried everything above and still can't connect, submit a ticket with the full output of ssh -v node-ip — it makes diagnosis much faster.
VNC Black Screen: Connected But No Desktop
  1. First confirm SSH still works — if it does, the machine is online and the issue is isolated to the display service.
  2. Over SSH, run sudo launchctl kickstart -k system/com.apple.screensharing to restart the screen sharing service, then reconnect.
  3. Black screen but the cursor moves: it's likely just stuck on the lock screen — type your account password and press Enter to reach the desktop.
  4. Screen looks garbled or refreshes extremely slowly: lower the client's color quality and drop the resolution to 1920×1080.
  5. Try a different client to cross-check (macOS's built-in Screen Sharing, or any standard VNC client). If both come up black, submit a ticket noting the result of restarting the service.
Runner Offline: CI Platform Shows Offline
  1. SSH in and run ./svc.sh status in the runner directory to check if the daemon is alive; if it's stopped, run ./svc.sh start.
  2. Check the latest log file in the _diag directory and search for "error" — most disconnect causes are spelled out plainly in the logs.
  3. If the log shows an authentication failure, the registration token has expired — run ./config.sh remove and re-register with a new token.
  4. If it drops mid-job, check whether concurrent tasks are exhausting memory. The 16GB configuration is best for a single concurrent job; for sustained multi-job concurrency, use the 64GB M4 Pro Workstation.
  5. Make sure you installed it as a persistent service with svc.sh, not running it in the foreground with run.sh — the foreground process exits when the SSH session disconnects.
Reinstalling macOS: Restoring the System to Factory State
  1. Reinstalling erases all data on the machine. Back up your build artifacts, certificates, and configs to your own storage first — backups are your responsibility.
  2. Log in to the console and submit a "Reinstall macOS" ticket noting your order number and node; no need to also email us.
  3. The instance is temporarily unavailable during reinstallation. Once complete, new credentials are sent automatically to your inbox — just follow the "First Boot" flow to reinitialize.
  4. Reinstalling is a user-initiated action, so your billing cycle continues as normal — it doesn't trigger any compensation time.
billing://faq

Billing & Invoices: Provisioning Time and Reading Your Invoice

All prices are listed in USD, with daily/weekly/monthly/quarterly cycles; add-ons bill in sync with your main cycle. Here are the two questions support hears most.

Can't make sense of your invoice?

The "Pricing" page has a fully annotated sample invoice (the invoice breakdown block): billing cycle, node, add-on line items, total — with a note on what each line means and how renewal/expiry is calculated. For example, the M4 Home monthly plan is $97.1, and a 1TB SSD add-on is $14.1/month, each shown as its own line item.

Open the invoice breakdown →

Paid — how long until it's live?

Card payments (Visa / Mastercard / Amex, via Stripe) confirm instantly upon authorization; USDT-TRC20 requires on-chain confirmation, usually 1–3 minutes. Once payment is confirmed either way, the system automatically provisions your machine — from payment to credentials delivered typically takes about 4 minutes in total. If it's been more than 15 minutes with no activation, submit a ticket with your transaction hash or payment receipt.

See full pricing →

We only accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), all settled in US dollars (USD); the actual available gateways are whatever the checkout API returns at order time.

USDT·TRC20 VISA AMEX stripe
ticket://sla

Tickets & Response Times: Have This Ready Before You Reach Out

Still stuck after working through the checklist? Time to reach a human. There are only two channels — send the right info once, and you usually won't need to follow up.

Console Ticket (Recommended)

Submit a ticket from the console — it's automatically linked to your order and instance, so it's handled fastest. Most tickets get a first response within a few hours, and a resolution plan within 24 hours.

Log in to submit a ticket

Email support@opsmac.com

Best for pre-sales questions or account login issues that keep you out of the console — replies within 24 hours. Please use a clear subject line and paste the exact error message in the body.

support@opsmac.com

Have These 4 Things Ready

Node (e.g. Tokyo), model (M4 Home / M4 Pro Workstation), order number, a description of the issue, and reproduction steps. If you have logs or ssh -v output, attach those too.

More complex issue? Go to "Who Do I Talk To" →
status://nodes

System Status: Node Status & Incident Notices

Same status page shown on our homepage: all four physical nodes are online, with no scheduled downtime reserved at any point in the year.

status://nodes — 4/4 online
SingaporeSG-01 · Singapore
online
Japan (Tokyo)JP-01 · Tokyo
online
South Korea (Seoul)KR-01 · Seoul
online
Hong KongHK-01 · Hong Kong
online

Available 365 days a year. If a hardware or network incident does occur, we post updates via email and a console banner, and compensate the affected lease per our "downtime credit" policy — see the full terms on "What Are the Rules".

changelog://recent

Recent Updates: Hands-On Tutorials & Buying Notes

Longer reads beyond these guides live on the blog: archived by month, with tutorials that include real-world timing benchmarks. Here's what's new in the last three months.