Got your setup details? Check the node, address, and port, then choose Screen Sharing, VNC, or SSH for your operating system. These steps also cover first-time setup, security, and common issues.
If you can’t connect, check the address and port first. Once you’re at the desktop, move on to security, display quality, or developer tools.
Check the address, port, and initial credentials in the instance details in your console. Never paste credentials into public chats or code repositories.
Connected, but the screen looks too small? Adjust the client’s scaling before increasing the remote resolution.
If your client has separate host and port fields, enter them separately. Don’t paste the full address into the host field.
Get the SSH host, SSH port, and VNC port from the instance details, then set the corresponding environment variables on your computer. The command below forwards the remote VNC service to local port 5901; keep the terminal window open, then connect your VNC client to 127.0.0.1:5901.
ssh -N -p "$SSH_PORT" -L "5901:127.0.0.1:$VNC_PORT" "$MAC_USER@$MAC_HOST"If local port 5901 is already in use, choose an available port and update the VNC client to match. Check the instance details for the actual SSH and VNC ports.
Complete these steps in remote macOS. Before changing sharing or firewall settings, keep your current session open and make sure you have another way to reconnect.
After signing in, change the current user’s password in System Settings. For team handoffs, use separate accounts instead of sharing the initial credentials.
To encrypt the disk, turn on FileVault under Privacy & Security and store the recovery information safely. First make sure you can still sign in remotely after a restart.
After enabling the firewall, keep only the access methods your work requires, such as Screen Sharing and Remote Login. Test each connection before removing other rules.
Add your public key to the remote user’s authorized keys file. After confirming key-based login works, adjust the password login policy.
In System Settings, open Sharing and turn off file sharing and remote management if you don’t use them. Don’t disable Screen Sharing or Remote Login if you rely on either.
Lag while dragging windows doesn’t necessarily mean your Mac lacks processing power. First check for display latency, network jitter, or resource-heavy build tasks.
Keep the default desktop resolution to start, and use client-side scaling to fit your screen. Increase the remote resolution if you need to view Xcode and the simulator side by side. More pixels generally require more bandwidth.
For static code editing, prioritize crisp text. If the network is unstable, switch to your client’s low-bandwidth or lower-quality mode. Test input response and scrolling after each change, and avoid changing several settings at once.
Choose a node close to the person doing the work, not just the team’s headquarters. Our locations include Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US East Coast. Test your connection to candidate nodes before connecting across continents.
Available Mac and node combinations are shown in real time in the console. To discuss moving an active instance, submit a ticket with your current node, target node, and acceptable downtime.
All nodes run year-round, 24/7. The details below explain our service commitment and how uptime is calculated; they are not live monitoring data.
These periods help you identify when to check; they don’t show daily status or measured uptime. Refer to console records to verify specific incidents and their duration.
Service credits: If monthly uptime falls below 99.9%, we’ll extend your service by 10 times the duration of the outage. Include the instance, node, and start and recovery times with your request so we can verify it.
Change one thing at a time. Note the exact error and when it occurred. These details are much more useful in a support ticket than “can’t connect.”
First confirm the Xcode version your project requires, then install command-line and package manager tools. Import signing assets last to avoid setting them up again if you change versions.
Open Xcode to check its version and component status, then run xcode-select -p to check the active developer directory. If the project pins a version, match it before building.
Use your project documentation to set up tools such as Homebrew, Ruby, and CocoaPods. Record their versions, then verify dependencies with a build that doesn’t require signing.
Import your team-authorized signing certificate into the remote keychain, set appropriate access permissions, then import the matching provisioning profile. Never put private keys or passwords in a repository.
Verify dependency installation, a simulator build, and the signing archive workflow in order. Record the Xcode version, failed command, and full error excerpt for troubleshooting.
Existing customers can sign in to the console to submit a ticket. For pre-sales questions or if you can’t sign in, email support@xcodevnc.com. Never include passwords or private keys in your email.
If you still can’t connect after checking the address and port and trying another network, SSH works but the desktop stays black, or the same issue repeatedly disrupts a build, tell us the impact and urgency in your ticket.
Check billing, renewals, and receipts in the console. Payments are accepted in USD via USDT-TRC20 or Visa, Mastercard, and Amex processed by Stripe. Available payment options are confirmed in the console.
Still choosing a setup? Compare the specs and term pricing for the two M4 tiers. Already ordered? Get the latest connection details in the console.