Enter an error snippet, tool name, connection method, or order topic. This guide covers first-time connections, permissions, macOS operations, Xcode builds, node networking, storage upgrades, billing, and payments.
Seven topic groups are expanded at once, so you don't need to filter them one by one. Start with the topic closest to the symptom, then narrow it down in the recommended order.
Confirm the host address, connection port, and account name from your order. For the first SSH connection, verify the fingerprint manually; for VNC, establish a baseline with the default resolution and medium image quality.
Troubleshoot connectionIf you can log in but can't write to a directory, check the file owner, directory permissions, and execution identity. If you can't log in at all, check credentials, key permissions, and the connection target first.
View diagnostic pathCheck available disk space, memory pressure, CPU-heavy processes, and the system time zone. Before changing versions or toolchains, record the current state to avoid changing multiple variables at once.
View initial setupRecord the Xcode version, scheme, configuration, target platform, and original command. Analyze the log from the first clear error instead of capturing only the final failure summary.
Open build guideA single ping doesn't represent the interactive experience. Sample continuously and watch the median, jitter, and packet loss while ruling out local Wi-Fi, proxies, upload jobs, and high-quality remote desktop traffic.
Compare node routesSeparate source code, dependency caches, build artifacts, and media files. Before expanding storage, record available space and daily growth, then decide whether to choose +1TB SSD or +2TB SSD.
View add-onsDon't provide only the total for a billing issue. Also record the order ID, model, billing term, selected node, SSD expansion, and Thunderbolt 5 add-on.
View order detailsDon't change the client, network, and credentials at the same time. Change one condition per test and retain the corresponding timestamp and error text.
If you see Permission denied or key authentication fails, verify the username, private key file, key permissions, and whether the wrong host was selected. Don't keep guessing credentials.
When the connection times out or is refused, verify the address and port first, then test from another network. A timeout usually means the path is unreachable; an immediate refusal means the target is reachable but the port isn't accepting connections.
If the session connects but shows a black or distorted screen or severe lag, lower the resolution and image quality, stop large background transfers, then disconnect and reconnect.
If the same node works on a mobile hotspot but not on an office network, check the local firewall, proxy policy, egress restrictions, and Wi-Fi packet loss before switching cloud nodes.
Build logs are only useful with context. At minimum, provide the tool versions, command, working directory, target, and first failure point together.
| Issue type | Check first | Recommended action | Information to retain |
|---|---|---|---|
| xcodebuild | scheme, configuration, destination, SDK, and working directory | Rerun the same complete command and investigate from the first clear error | Command, exit code, Xcode version, failure context |
| fastlane | Ruby environment, dependency lockfile, lane parameters, and working directory | Use the project's locked dependencies first; avoid temporarily upgrading the entire toolchain | Lane name, invocation parameters, dependency versions, original output |
| Signing environment | Certificate validity, provisioning profile match, and keychain access permissions | Verify the bundle identifier, team settings, and target configuration; don't upload unsanitized signing materials | Target name, signing method, sanitized error text |
| Cache cleanup | DerivedData, package manager caches, and available disk space | Clear only caches related to the failed target; avoid resetting the entire environment | Commands before and after cleanup, available disk space, dependency resolution result |
| Log collection | Time range, time zone, command exit code, and result bundle | Save text logs and necessary result bundles; use screenshots only as supplementary evidence | Time of occurrence, reproduction steps, first error and surrounding output |
If the failure occurs only in an automated job, run it manually once with the same working directory, environment variables, and dependency versions. If it succeeds manually but fails in the queue, compare the execution identity, working directory, and injected environment.
xcodebuild -scheme App -configuration Release build
echo $?
sw_vers
xcodebuild -versionThe current catalog includes Singapore, Tokyo, Seoul, Hong Kong, and US West only. Both models are available in all five nodes; actual availability is returned in real time by the console.
Suitable for workflows whose primary users are in Southeast Asia. When comparing nodes, run continuous tests on the actual office network instead of relying only on geographic distance.
Southeast AsiaSuitable for interactive workloads targeting Japan and East Asia. For long VNC sessions, monitor latency, jitter, and display bitrate together.
Japan & East AsiaSuitable for South Korea and Northeast Asia. If SSH responds normally but the display lags, lower the remote desktop quality and pause background transfers first.
South Korea & Northeast AsiaSuitable for South China and parts of Southeast Asia. Corporate and home networks may use different egress routes, so test on the network you will actually use before choosing a node.
South ChinaSuitable for the North American West Coast and workloads that need to be close to local collaboration routes. For cross-continental access, assess interactive latency before large-file transfer performance.
North American West CoastStart with a geographically nearby node, then run continuous samples on the same network and at the same time. Compare median latency, jitter, packet loss, and VNC responsiveness. For teams working across regions, choose based on both the primary users and the direction of large-file transfers.
Order configuration determines what is delivered; payment records determine settlement status. When submitting an issue, provide both sets of information instead of sending only a payment screenshot without the order ID.
Check the order ID, Lemon M4 or Lemon M4 Pro, daily/weekly/monthly/quarterly term, selected node, SSD expansion, Thunderbolt 5 add-on, and current service status in order.
All orders are settled in USD. The actual available gateway is determined by the backend response. Only these two channels are supported:
If the payment and order statuses don't match, retain the order ID, payment time, amount, and a sanitized transaction record. Do not submit complete card details or access tokens.
Remove private keys, seed phrases, complete access tokens, and unsanitized signing materials. The support team needs reproducible information, not sensitive credentials.
Provide the order ID visible in the console; don't provide only the model name or payment amount.
State when the issue occurred and the time zone; for intermittent issues, also record the most recent time it worked normally.
Specify Singapore, Tokyo, Seoul, Hong Kong, or US West, and state the region where the primary users are located.
Starting from a known-good state, list commands, interface actions, and the failure point in the order performed.
Provide copyable error text whenever possible. Screenshots should include necessary context, and logs should retain the output before and after the first error.
Explain separately what you expected, what actually happened, and whether the issue can be reproduced consistently.
Submit a ticket after logging in to the console to associate it with an existing order and service status, or email support@lemonvm.comfor pre-purchase selection advice or when you can't log in to the console.
Both models, all five nodes, and daily, weekly, monthly, and quarterly terms are clearly shown during checkout. After purchase, view the configuration and service status in the console.