Connectivity
SSH or VNC cannot establish a session
For connection timeouts, changed host fingerprints, rejected credentials, interrupted graphical sessions, or abnormal displays after reconnecting.
View connection diagnostics
Support Center
Identify the issue first, then choose the next step
This guide brings together solutions for RunnerVPS Cloud Mac connectivity, system, networking, storage, build, and account issues. Search by symptom first, then follow the diagnostic path step by step to avoid changing multiple variables at once.
Documentation version 2026.09 covering 5 available nodes
RUNNER SUPPORT
Connection diagnostic receipt
Check in order
A
Confirm device status
Verify the device ID, region, and current access status
Start
B
Separate access paths
Test SSH and the graphical interface separately
Route
C
Collect reproducible evidence
Record the time, errors, network environment, and redacted logs
Handoff
- Guiding principle
- Change one variable at a time
- Escalate to support
- Submit a ticket linked to the device
Issue categories
Match symptoms to the right check
All six categories are shown at once, so there is no need to switch filters. Each card lists common symptoms, priority checks, and the relevant section on this page.
System
Toolchain versions have changed
For incorrect Xcode selection, drifting command-line tool paths, incompatible dependencies after a system update, or failed environment variables.
View system checks
Networking
Pulls, uploads, or port forwarding fail
For interrupted Git pulls, failed SFTP transfers, unreachable SSH tunnels, DNS resolution issues, or local network restrictions.
View transfer guidance
Storage
Build caches fill the local disk
For growing DerivedData, archives, dependency caches, or logs that cause build failures, interrupted exports, or slower writes.
Check disk space
Builds
Signing, archiving, or automation tasks fail
For mismatched certificates and signing files, inconsistent runner environments, polluted dependency caches, or missing archive artifacts.
View build checks
Account
Orders or device records need verification
For cases where the rental status, device ID, order record, notification email, or ticket association needs confirmation.
Open the console
Connection diagnostics
Narrow the fault using the same sequence
Do not reset credentials, change networks, and modify system settings at the same time. Preserve the original error, perform one check at a time, and compare the results.
01
Node status
In the console, verify the device ID, region, rental period, and access status. Confirm that you are working on the intended device and record when the status changed.
02
Access credentials
Verify the username, SSH private-key path, and file permissions. Do not paste private keys, passwords, or complete connection credentials into email, chat, or ordinary logs.
03
SSH channel
Verify the host fingerprint first, then use verbose output to identify where the connection fails. Distinguish DNS, TCP connection setup, key exchange, and user authentication instead of relying on “connection failed” alone.
04
Graphical session
When SSH works but VNC does not, check the client address, session status, and resolution settings. After a disconnect, wait for the original session to release before reconnecting to the same device.
05
System firewall
Confirm that the processes required for remote access are still running and that the relevant ports are listening as expected. Save the current configuration before changing rules so you can roll back if the issue worsens.
06
Local network
Only then switch local networks for comparison. Temporarily disable proxies or VPNs that may rewrite routes, and compare results on corporate, home, and mobile-hotspot networks.
Remote desktop
Make graphical sessions recoverable and easy to hand off
VNC is useful for work requiring Xcode, previews, and graphical tools. Make sure the SSH channel works first, so command-line checks remain available if the graphical session fails.
Prepare a controlled VNC client
Install the client from a trusted source and save the device name rather than sharing complete credentials. On the first connection, verify the target region and device ID, then confirm encryption and keyboard-mapping settings.
- Save the device name and access address separately
- Team members should use individually controlled access methods
- Prefer connecting through a controlled network or SSH tunnel
Adjust resolution before judging performance
Remote display performance depends on resolution, color depth, and the local network. Lower the display area first for comparison; do not change the client, network, and system display settings at the same time.
- Start with a lower resolution to test input response
- Avoid evaluating display performance while transferring large files
- Record the last setting changed before the issue appeared
Lock the session instead of force-quitting processes
Lock the graphical session when stepping away briefly, rather than closing an application that is still building. After reconnecting, confirm the original task status before deciding whether to restart the tool.
- Save the project and uncommitted changes before leaving
- Do not restart a task immediately because the display is frozen
- Revoke a team member’s access promptly after they leave
Build environment
Pin the toolchain, then clean reproducible data
Continuous builds are most vulnerable when the environment changes between tasks without a record. Document version selection, signing materials, and cache cleanup in the team runbook.
Pin Xcode and the command-line tools
Record the Xcode version in the project configuration and runner initialization script, and verify the active developer directory before running a task. After a system or Xcode change, run a minimal test task before restoring the full pipeline.
Separate certificates, signing files, and the code repository
Certificates, signing files, tokens, and environment variables should be injected through your team’s own secrets-management process. Do not commit long-lived credentials to Git or forward raw logs containing sensitive fields as ordinary attachments.
Clean caches by source
First identify whether space is used by DerivedData, dependency caches, archives, simulator data, or project assets. Prioritize deleting regenerable data while preserving build artifacts and evidence that still need to be transferred.
Environment checklist
Before running a task
- Xcode
- Matches the version and project constraints
- Developer directory
- Points to the target toolchain
- Signing materials
- Injected temporarily for the task
- Disk space
- Covers caches, archives, and exports
- Minimal test
- Verify pulls, compilation, and artifact generation first
Change one thing at a time
Write results to the build log
Network and files
Verify connection and file channels separately
Use a small file first to verify the path and permissions, then transfer the full repository, assets, or build artifacts. If it fails, record the direction, size, time, and exact stage.
Forward only the ports you need
Specify the local port, target address, and purpose to avoid broad listeners. After creating the tunnel, verify SSH itself and the forwarded service separately to distinguish authentication issues from application issues.
Confirm directory permissions first
Use a dedicated project directory for incoming files. Upload a small sample first and verify read/write permissions. After a large file finishes, check its size or checksum; do not treat the client progress bar as the only confirmation.
Limit repository credential scope
Use least-privilege credentials for automation and restrict them to the required repositories. If a pull fails, check DNS, remote reachability, host fingerprint, credential permissions, and repository address separately.
Clean up source files only after transfer
Attach the task ID, version, and checksum information to each artifact. Confirm that the destination has received it completely before removing intermediate files from the node, so the original result can be reproduced if needed.
Knowledge articles
From operating procedures to team strategy
The articles below are sorted by publication date, covering system upgrades, connection security, service selection, audio and video, Unity iOS builds, and M4 development task observations.
Knowledge articles are being organized
Before the full articles are published, use this page’s connection diagnostics, system checks, network transfer, and build environment checklists.
Human support
Put tickets in a state that can be investigated immediately
For technical issues, submit a ticket through the console first so it can be linked to the specific device and order. If you cannot sign in, email support@runnervps.com, but do not include passwords, private keys, or complete payment credentials.
Device ID
The device name shown in the console; do not send the access password
Region
Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or the Eastern United States
Issue time
Include the time zone and the time range of the last known-good operation
Reproduction steps
List commands, actions, and actual results in execution order
Redacted logs
Remove tokens, keys, passwords, repository credentials, and personal data
Need a dedicated M4 to reproduce an issue?
Runner M4 and Runner M4 Plus are dedicated physical machines, not virtual machines, available for daily, weekly, monthly, or quarterly rental. Actual availability is determined by the console in real time.