Troubleshoot, then take action

Having trouble with your remote Mac?
Find your next step here

Troubleshooting a first connection, a laggy display, or a renewal? Start with the steps for your issue. Your Mac runs on a dedicated Apple Silicon physical machine, so you can troubleshoot desktop access and command-line access separately.

Need to check the address or credentials for an existing instance?Log in to the console, then open the relevant instance details.

Getting connected

Choose a connection method for your computer

Default protocol ports explain how connections work; they don’t guarantee your instance uses those ports. Always use the address and actual port shown in the console. Don’t expose services to the public internet unless they’re open for access.

macOS Screen Sharing

Ideal for controlling a remote desktop from a local Mac. VNC uses TCP port 5900by default. If your instance uses a different port, add the actual port to the address.

  1. Open the instance details in the console and copy the host address, desktop port, and instance username.
  2. Create a new connection in the local Screen Sharing app, or open Finder’s “Go → Connect to Server” and enter vnc://HOST:PORT.
  3. Sign in with your instance credentials. On your first connection, open a regular folder and check that the mouse, keyboard, and display respond as expected.

If the connection stays stuck, check the address and port, then try another local network. If authentication fails, check the instance username and password first.

Use VNC on Windows

Use a VNC client that supports your instance’s authentication method to connect to the macOS desktop. The default port is also TCP port 5900, not the Windows Remote Desktop Protocol.

  1. Install a VNC client, then copy the host address, actual port, and instance credentials from the console.
  2. Enter the host and port in the fields required by your client. Clients may interpret colon-separated addresses differently, so use separate host and port fields when available.
  3. After authenticating, select “Fit to window,” then adjust scaling and image quality for your screen. Avoid starting with the highest image quality.

If authentication succeeds but the desktop doesn’t appear, note the client name, version, and full error message. Don’t cycle through incompatible authentication modes or expose your password in screenshots.

Connect over SSH

Ideal for builds, log checks, and running scripts. SSH uses TCP port 22by default. If the console provides a custom port, use -p to specify it explicitly.

  1. Make sure the console has provided SSH connection details and that remote login is available.
  2. In a local terminal, run ssh -p PORT USER@HOSTand replace the three uppercase fields with the values in your instance details.
  3. On your first connection, verify the host fingerprint. After authenticating, run whoami and pwdto confirm your user and working directory.

For a timeout, check the network and port first. For “connection refused,” check the service status. If authentication fails, check the username and credentials. After reinstalling, verify any changed host fingerprint against the instance before proceeding—don’t dismiss the warning.

File transfers with SFTP

SFTP and SCP transfer files over SSH and use TCP port 22by default, so there’s no separate file-transfer port to guess. Use the same username, host, and actual port as for SSH.

  1. Select SFTP in your file transfer client, then enter the instance address, SSH port, and instance username.
  2. Upload a small file first to a directory you can write to. Check the path, file size, and downloaded result.
  3. Transfer large projects or assets in batches, then verify important files. For a custom SCP port, use uppercase -P—for example: scp -P PORT ./file USER@HOST:~/.

Don’t use the desktop clipboard to transfer large files. Before your rental ends, download your code, assets, build artifacts, and any configuration you need to keep.

Service level and records

Keep the uptime commitment separate from live status

All five regions operate year-round, 365 days a year. Service levels are calculated monthly. Troubleshoot desktop client lag, issues with your own network, and full machine outages separately.

99.9%

Monthly uptime commitment

Records for the past 90 days—not a monthly billing result

The sections below show the date range for records from each region over the past 90 days. This page isn’t connected to live monitoring, so it doesn’t show continuous uptime history or present the commitment as measured uptime. Check your instance’s current status in the console.

Singapore

Monitoring records for the past 90 days haven’t loaded
Not live

Tokyo, Japan

Monitoring records for the past 90 days haven’t loaded
Not live

Seoul, South Korea

Monitoring records for the past 90 days haven’t loaded
Not live

Hong Kong

Monitoring records for the past 90 days haven’t loaded
Not live

US West

Monitoring records for the past 90 days haven’t loaded
Not live

If monthly uptime falls below 99.9%, service credits are calculated based on the duration of the outage. To request a review, provide your instance ID and the outage start and end times, including the time zone. Final calculations are subject to the service terms.

FAQs

Find answers by symptom, not guesswork

Find separate guidance below for connections, credentials, system tasks, billing, and payments. For order- and instance-specific details, check the console after signing in.

Connection and display lag

Can’t connect with Screen Sharing or VNC? What should I check first?

First, check whether the instance is provisioned in the console. Then verify the host address, desktop port, and username. Make sure there are no spaces at the beginning or end of the copied details, and don’t use an address saved from an old order. Check that your local firewall, corporate network, or proxy isn’t blocking the port.

Next, try another local network and test SSH. If SSH works but the desktop doesn’t, check the desktop service, client authentication method, and image quality settings. If both fail, submit the instance ID and the full error messages from both connection methods—not just “it won’t open.”

Connected, but the display is laggy or doesn’t respond smoothly?

Lower the client’s image quality or desktop resolution first. Pause large local uploads and downloads, then retry the same action. Remote desktop performance depends on network round-trip time, packet loss, encoding, and local decoding; a single latency number can’t tell you how well the machine is performing.

If things slow down only during builds, inference, or asset exports, check CPU use, memory pressure, and disk use in Activity Monitor on macOS. In your support ticket, include the task, how often the issue occurs, your client version, and whether it persists on another network. This helps identify whether the bottleneck is the network or workload.

Accounts and credentials

Why does the remote machine reject my password when I can sign in to the console?

Your console account is for orders, billing, and support tickets. The instance username and password connect to your Mac; the two sets of credentials aren’t interchangeable. Open the relevant instance details to find its connection information, and check your keyboard layout, capitalization, and copied text.

After changing your instance password, clear the old saved password from your client before reconnecting. After reinstalling the system, check the instance details again instead of using locally cached credentials. Support will never ask you to email your password, verification code, or private key.

Reinstall and recovery

What’s the difference between restarting and reinstalling? Can I recover my files afterward?

A restart interrupts your current session and running tasks, and is usually used to restore system responsiveness. A reinstall deploys the system again and may erase existing files, tools, and settings. Don’t reinstall just to fix a single connection issue—check the address, credentials, and client first.

Before reinstalling, download any data you need to keep to a location outside the instance, then check that your backup files open. After reinstalling, restore only from a backup you’ve verified; don’t count on recovering the original disk contents. Follow the task progress in the console while you wait, and don’t submit the same request again.

Billing and invoices

How do I renew? Can I switch from daily to monthly billing?

First, check the instance expiry date, region, and current order in the console, then review the available renewal and billing cycle options. List prices for Pull M4 are $20.4/day, $55.2/week, $102.2/month, and $278/quarter. Pull M4 Pro is $59.7/day, $161.2/week, $298.6/month, and $812.2/quarter.

Whether you can change the billing cycle on your current order, and when the change takes effect, depends on the options available in the console. If you don’t see the option you need, submit your order number and preferred cycle to ask about next steps. Don’t assume the unused portion of your current cycle will be credited automatically. There’s no charge if you don’t renew at expiry, but make sure to renew or back up your data before then.

What billing and invoice details do I need for team expense claims?

All charges are billed in US dollars (USD). Save your order, billing, and payment records from the console, then provide your billing reference, requested billing details, and delivery information. The records shown and invoice details available depend on your order and what support confirms.

A payment screenshot isn’t a substitute for an order record. If the amount differs from what you expected, check the model, billing cycle, added storage, and Thunderbolt 5 daisy-chain configuration. Include any line items you’re unsure about in the same support ticket.

Payments and order status

Which payment methods do you accept? What if my order hasn’t updated after payment?

We accept USDT-TRC20 and Visa, Mastercard, or Amex through Stripe. Available payment gateways are determined by the backend response. For USDT-TRC20, verify the network, payment address, and amount due. For card payments, follow the authentication prompts on the payment page.

Check the order record in the console for payment status. If it hasn’t updated yet, keep your billing reference and payment time, and don’t pay again. For USDT-TRC20, you can provide the transaction hash. For card payments, provide the payment result or error message with sensitive information redacted. Never send your full card number, security code, or account verification code.

System tasks

Save your work before changing the whole machine

Start these tasks from the instance details after signing in. Your console account password and instance connection password are managed separately. Before taking action, verify the instance ID—not just the model name.

Restart an instance

Save your files and stop builds, uploads, and exports. Open the instance details in the console, verify the instance ID, then select Restart and confirm. Your current connection will drop. Wait for the instance to come back online, then test using your usual connection method.

Estimated time:Follow the task progress in the console. System startup and app recovery take additional time, so a successful submission doesn’t mean the desktop is ready. If it doesn’t recover after an extended wait, note when you started the operation and submit a support ticket. Don’t keep restarting it.

Reinstall macOS

First, verify your backup on another machine, then check the available reinstall options in the instance details. Read the data removal notice, verify the target instance, and confirm. When the task finishes, get the connection details again, check your tool versions, and restore your projects and settings.

Estimated time:Use the estimate and status shown for the current task in the console. Reinstalling includes system deployment and initialization, so it involves more steps than a regular restart. This page doesn’t promise a fixed completion time. Don’t start a reinstall just before a release or delivery deadline.

Reset the instance password

Open the relevant instance details and check whether a password reset option is available. Verify the target username, then reset the password. Wait for the task to finish before updating saved credentials in your desktop client and automation scripts. If you don’t see the option, request help through a console support ticket.

Estimated time:Wait for the operation to finish, then authenticate again with the new password. Don’t keep trying the old one, and remember that resetting an instance password doesn’t change your console account password.

Data and security

Treat the instance as your workspace; keep backups elsewhere

On a dedicated physical machine, the CPU, GPU, and memory are reserved for one tenant—but a dedicated machine isn’t a backup. When your rental ends, the disk is erased, and the next tenant won’t inherit your working environment.

Before expiry: download and verify

Keep your source code, assets, build artifacts, and essential configuration. Export any uncommitted changes stored only on the machine. Copy your backups somewhere outside the instance, then open a few important files to verify them. Don’t rely on a successful archive upload without checking its contents.

Record what you backed up, when it finished, and how to restore it. For team handoffs, have the next person open the files. A saved remote desktop session isn’t a completed handoff.

At the end of your rental: don’t rely on the original disk

Decide whether to renew or stop using the instance before it expires. When your rental ends, the instance disk enters the erasure process; don’t count on erased data being recoverable. This page doesn’t provide an unverified erasure completion time or an individual instance receipt.

To check an order’s end status or ask about data handling, provide your instance ID and order number through a console support ticket. See the privacy policy for information about data use and how to submit requests.

Everyday security: limit access to credentials

Don’t put instance passwords, SSH private keys, build keys, or verification codes in public repositories, chat screenshots, or shared documents. Update relevant credentials when team members leave, and check whether old settings in your scripts can still access the instance.

In troubleshooting screenshots, show only the issue and error; redact passwords, access tokens, and sensitive payment information. If you need support to inspect files on your machine, specify the scope of access and the paths to check.

Get help from support

Include these details to avoid back-and-forth

For issues with a rented instance, submit a console support ticket so it can be linked to your order. For presales questions, team rentals, or login issues, email support. Neither channel will ask you to share your connection password publicly.

What to include in a support ticket

  • Instance and orderInstance ID, region, and the relevant order or billing reference. If you have multiple machines, specify which one.
  • Time and environmentWhen the issue occurred and the time zone, your local operating system, client name and version, and whether you tested another network.
  • Issue and evidenceThe full error message, screenshots with sensitive information redacted, and what changed before and after the operation.
  • Checks you’ve triedWhether you verified the address and port, whether SSH connects, whether you restarted, and the result of each step.

How to check support response times

Year-round regional operations don’t mean immediate replies from support. This page doesn’t publish unconfirmed response hours or minute-by-minute response times. Check your console support ticket for the latest response and progress.

If the issue is affecting an active build or delivery, include the scope of the impact and the task deadline. Add updates to the same ticket to keep the conversation together. Don’t assume a request has been received until you see a successful submission confirmation.

Our only support email is support@vpspull.com. Suggested subject: “Issue type + instance ID.” Use the checklist on the left to organize your message.

Ready to get started?

Choose how to connect,
then pick your remote Mac

Rent either model by the day, with Pull M4 starting at $20.4/day. Test your workflow on a real project first. Check the console for live availability by model and region.