Use SSH by default for command-line builds, automation scripts, and long-running tasks. When you need Xcode, graphical output, or desktop applications, open a browser-based remote session from the device details in the console.
DplyMini provides dedicated physical Cloud Macs. Each order maps to a physical node, not a virtual machine. Before connecting, verify the host address, username, and host fingerprint before transferring projects or running builds.
The connection method does not change the device configuration, but it affects efficiency, network sensitivity, and session recovery. Keep continuous tasks running in the background and reserve graphical sessions for steps that require a visible desktop.
Dependency installation, code checkout, compilation, testing, log inspection, and file verification are all well suited to SSH. During brief network disruptions, tmux, screen, or CI Runner can keep tasks running on the device.
When you need to open Xcode, inspect a simulator, adjust a graphical tool, or confirm a desktop app's state, start a remote session from the device details in the console. Continuous builds should not depend on an open browser tab.
A simple rule:If a step can be expressed as a command and needs to be repeated, prefer SSH; use browser-based remote access only when you must observe or operate the macOS graphical interface.
Do not try multiple usernames or repeatedly accept unknown fingerprints as soon as you receive an address. First confirm the delivery details in the device details in the console, then connect from your local terminal.
Each operator should use their own key; never copy private keys between team members. Use a modern key type and protect the private key with a local passphrase.
ssh-keygen -t ed25519 -C "deploymini-access"
The public key is usually found at ~/.ssh/id_ed25519.pub. Never upload or paste the private-key file into chats, code repositories, or ticket attachments.
cat ~/.ssh/id_ed25519.pub
Use the address, port, and username shown in the current order's device details. Do not reuse connection commands from another order or guess the address from the node name.
ssh -p <port> <user>@<host>
When your terminal asks whether to trust the host for the first time, compare the displayed fingerprint segment by segment with the information in the device details. If they do not match, stop and submit a ticket—do not enter yes.
SHA256:<fingerprint-from-device-details>
Delete the corresponding public key immediately when a member leaves the project, a device changes hands, or temporary collaboration ends. Do not let one long-lived shared key cover the entire team.
You can assign a device an alias in your local SSH config, but the host, port, and username must still match the current delivery details in the console.
If a known-host entry changes unexpectedly, first confirm whether the order or address changed. Until verified, do not delete the old record and accept the new fingerprint.
The clipboard is suitable for short text and one-time commands, not private keys, complete payment credentials, or large blocks of sensitive configuration. Clear local and remote clipboard contents after copying.
Start with a scaling level suited to the current window. Enter full-screen mode for precise work; if input latency increases, exit full screen, lower the resolution, and reassess the connection.
The example below shows a typical SSH session. The actual address, username, project path, Scheme, and export configuration depend on your order and project; do not copy the example parameters directly.
$ ssh -p <port> <user>@<host>
The authenticity of host cannot be established.
ED25519 key fingerprint is SHA256:<fingerprint>
Are you sure you want to continue connecting? yes
Connected to dedicated physical Mac mini
$ sw_vers
ProductName: macOS
ProductVersion: <installed-version>
$ cd ~/work/ExampleApp
$ xcodebuild \
-workspace ExampleApp.xcworkspace \
-scheme ExampleApp \
-configuration Release \
build
** BUILD SUCCEEDED **
$ bundle exec fastlane ios build
[fastlane] Resolving project configuration
[fastlane] Running archive workflow
[fastlane] Build artifacts ready for verification
$ shasum -a 256 ./output/ExampleApp.ipa
<checksum> ./output/ExampleApp.ipaRecord macOS, Xcode, Ruby, dependency-management tools, and the project's commit version. When results differ, compare the environment records before reinstalling all dependencies.
Record the output path, file size, checksum, and key build logs. Recalculate the checksum on the receiving end after downloading to confirm that the transfer did not change the file.
Verify one layer at a time and record the result of every step. This helps identify whether the issue is local resolution, the egress network, access rules, authentication, or a service on the device.
Confirm that the connection command uses the host address currently shown in the device details. If you use a hostname, first check that it resolves to the expected address and rule out a local hosts-file override.
nslookup <host>
Confirm that the current network allows outbound connections. Corporate networks, guest Wi-Fi, proxies, and VPNs can change the egress path; switch to a known-good network for comparison.
traceroute <host>
Verify the port provided with the order and check whether local security software or organizational network policies are blocking it. Do not assume every device uses the default SSH port.
nc -vz <host> <port>
Distinguish between an unreachable port and an authentication failure. For authentication failures, check the username, public-key path, key permissions, and ssh-agent instead of repeatedly trying different passwords.
ssh -vv -i ~/.ssh/id_ed25519 <user>@<host>
If the port is reachable but the session disconnects immediately, record the complete error shown before disconnection. If the browser session fails, also check whether SSH still connects to distinguish the graphical channel from the device's overall status.
Connection reset | timeout | permission denied
Finally, return to the console and verify the order, node, and device information. All nodes operate normally 365 days a year; use the real-time connection status returned by the console for current availability.
Do not use ping as your only conclusion.Some networks restrict ICMP, while the SSH destination port may still accept connections. Record the resolution result, destination-port test, and verbose SSH output together.
A dedicated physical machine reduces resource contention, but it does not replace internal access controls. Manage keys, temporary credentials, project data, and remote desktops with least privilege.
Start with personal keys and end with active revocation.
Support staff do not need your private key to troubleshoot connection issues. Never send private-key content by email, in chat history, through a code repository, or in a ticket attachment.
Keep the error type, command-parameter structure, timestamp, and client version; replace the host address, username, project name, and sensitive values with clear placeholders.
Browser-based graphical performance is mainly affected by round-trip latency, jitter, and available bandwidth. Build speed depends more on the project, cache, and device configuration, so assess the two separately.
Choose the node with the best end-to-end path to your team, code repository, and artifact storage. A brief period of low latency does not guarantee a stable session; jitter and packet loss also affect input responsiveness.
Transfer assets, models, and build artifacts in batches. Record the file count, total size, and checksums before and after transfer; retry only the parts that differ.
Run long compilations, tests, and encoding jobs in the background on the device, and write logs to files. Closing the browser or experiencing local network fluctuations should not interrupt the task.
If you cannot locate a connection issue using the sequence above, submit a ticket for the relevant order in the console. The more complete the information, the easier it is for support to reproduce the issue and identify the affected layer.
If the device cannot connect, the session repeatedly disconnects, or delivery information is incorrect, submit a ticket for the relevant order in the console instead of scattering order details across multiple email threads.
If you have not ordered yet or need to confirm the connection method, describe the expected task, target node, client environment, and planned rental term, then email support@deploymini.com.
Choose a configuration and one of the five nodes, then verify the connection details in the console after placing your order. On your first login, verify the host address, username, and fingerprint in the order shown on this page.