> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/backup-dr/vmware-import-downloads-fail-server-refused.md). # VMware Import Scans Succeed but File Downloads Fail ## Symptoms * The VMware Service connects to vCenter and scans VMs without errors. * A backup or import job starts, then pauses, retries, and fails after several attempts. * The service log shows the snapshot succeed, then a run of download errors: ``` Error: The server refused connection Error downloading file: [] /.nvram Error downloading file: [] /.vmxf Error downloading file: [] /.vmx Backup job paused due to encountering an error. Will retry again in approximately Nm (#k of 10) ``` * The failure hits **every** file, including the small config files (`.vmx`, `.vmxf`, `.nvram`) — not only the large virtual disks. {% hint style="info" %} **Why "Every File" Matters** If the small config files fail together with the disks, this is not a disk-specific or VDDK transport problem. It is a connection problem with the host that holds the files. {% endhint %} ## Overview {% hint style="info" %} **Key Points** * The VMware Service uses vCenter only to list VMs and locate their files. * The actual file transfer goes directly to the ESXi host, at the FQDN vCenter returns. * If the service cannot resolve or reach that host, the scan succeeds while every download fails. {% endhint %} The VMware Service uses vCenter only to enumerate VMs and locate their files. The actual transfer goes directly to the ESXi host that owns the VM's datastore, at the host FQDN that vCenter returns. If the service can reach vCenter but not that ESXi host, vCenter looks healthy — the scan succeeds — while every download fails with "server refused connection". There are two common causes. **1. DNS.** The VMware Service cannot resolve the ESXi host FQDNs that vCenter returns. The usual reason is a wrong or missing DNS server or search domain on the service VM's NIC. This is the most common cause. It also explains why VMs on one cluster back up fine while another cluster fails — the working cluster's hosts happen to resolve. **2. Network or firewall.** The host name resolves, but the host is not reachable directly. The transfer needs TCP 443 (vSphere API) and TCP 902 (NFC, the disk data channel) open from the VMware Service to each ESXi host, not only to vCenter. Port 902 is the one most often missed. ## Diagnosis 1. In vSphere, note the FQDNs of the ESXi hosts in the cluster that owns the failing VM's datastore. These are the names VergeOS connects to. 2. In VergeOS, navigate to **Import/Export > VMware Services** and double-click the service. 3. Select **View Service > Diagnostics**. 4. From the Diagnostics panel, try to resolve and reach each host FQDN. * If a name does not resolve, the cause is DNS. * If a name resolves but does not connect, check the firewall and port 902. ## Solution 1. Set the VMware Service VM's NIC to a DNS server that resolves the ESXi host FQDNs, or add the correct search domain. See [Configuring VMware Service VM NIC IPv4 Settings](/knowledge-base/networking/vmware-service-vm-nic-ipv4-configuration.md). 2. Make sure TCP 443 and 902 are open from the VMware Service to each ESXi host, not only to vCenter. 3. Run the job again. The downloads proceed past the config files and into the virtual disks. ## Additional Resources * [Configuring VMware Service VM NIC IPv4 Settings](/knowledge-base/networking/vmware-service-vm-nic-ipv4-configuration.md) * [VMware Backup and DR Guide](/knowledge-base/backup-dr/vmwarebackupdrguide.md) {% hint style="info" %} **Need Help?** If downloads still fail after you confirm DNS and the ports, contact the VergeOS support team with a copy of the VMware Service log. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.verge.io/knowledge-base/backup-dr/vmware-import-downloads-fail-server-refused.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.