Find the right checks for connection, development environment, or order issues. Check access addresses and authorization details in your console order; this page contains no real credentials.
This is an informational index. Node details and order status are based on the information returned by the console.
Search finds topics on this page; it does not look up your orders or access credentials. For instance-specific issues, check your console.
If the node or connection method in your records doesn't match the order, use the information currently shown in the console. Don't post addresses or credentials in public forums.
Note which step the issue starts at, then change one thing at a time and test again. Network routes, clients, and workload can all affect your experience; we don't publish unverified latency figures.
Check the address and connection method in your order, confirm your local network and client are working, then make sure your account has access to the instance.
If the client shows an error, save the exact message and note when it occurred. Avoid changing several settings at once, or it may be hard to tell what fixed the issue.
Prepare troubleshooting notesNote whether the screen is black, scaled incorrectly, or not responding to input. Check the client's display settings and make sure your local network isn't switching frequently during the session.
If you can use the desktop, save your work first, then start a new session as described in your order. Don't assume a display issue means the node is faulty.
Screenshot redaction guideNote when it disconnected, what you were doing, and any client message. Check whether your local network switched or dropped, then verify the task status after reconnecting.
Don't rely on the desktop view alone to tell whether a build or experiment finished. Check the project logs and artifact directory to avoid running it again unnecessarily.
Check tasks and logsCheck the console for the macOS and software versions available on your physical node. Record the current setup before making changes to meet project requirements. Don't mistake a project dependency issue for a remote connection problem.
Check the system version on the desktop against your project's and tools' minimum requirements. Record the full version number, not just “latest.”
Check the Xcode version in use, project requirements, and required SDK. If multiple versions are installed, confirm which one the build job actually uses.
Run xcode-select -p and xcodebuild -version, then compare the paths and versions with what you expect. Before changing the selection, consider the impact on other tasks.
Check the lockfile, package manager version, and project scripts. Verify dependencies with a reproducible minimal task before deciding whether to clear the cache.
Check these five stages separately: code checkout, dependency installation, compilation, signing, and artifact handling. With a self-hosted runner, also check the run account's permissions, working directory, and how secrets are injected securely.
Keep the failed command, exit status, and redacted logs. Don't include signing materials or raw environment variable values in a support ticket. If the desktop works but the build fails, start with the project logs.
Consistent terminology makes it easier to distinguish the machine, location, connection method, and billing choice when describing an issue.
Start with the term and add-ons selected in your order, then check the final amount shown in USD. The plan page lists full-term prices and add-ons; don't estimate an order using the price for a different term.
All orders are billed in US dollars (USD). Check the model, term, add-ons, and final amount together in the same order. Prices are listed separately by term and aren't calculated by simply multiplying a daily rate.
We accept USDT-TRC20 and Visa / Mastercard / Amex processed through Stripe. The payment options available at checkout depend on what the backend returns. If a payment doesn't complete, check the order status before trying again.
First, visit the Plans & Pricing page to view the available options, then check the selected term, node, and add-ons in your console order. The order confirmation is the source of truth for what you purchased.
For issues with an existing order, submit a support ticket from the console. Include the checks you've already completed so support can continue with the steps that haven't been ruled out.
Never send passwords or keys.If more information is needed, continue the conversation only through a console support ticket. For general pre-sales questions, you can also email support@vpspush.com.
For an existing order, sign in to the console and submit a support ticket with the checks you've completed. For pre-sales questions, visit the contact page to find the right way to reach us.