---
title: "Failed initial push to Platform | Lansweeper Classic"
slug: "troubleshoot-a-failed-initial-push-to-cloud"
description: "Troubleshoot a failed initial push when linking Lansweeper Classic to a Lansweeper Platform site. Retry the push, relink, and check the sync log files."
updated: 2026-06-25T19:52:37Z
published: 2026-06-25T19:52:37Z
canonical: "docs.lansweeper.com/troubleshoot-a-failed-initial-push-to-cloud"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lansweeper.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot a failed initial push to Lansweeper Platform

When you [link your Lansweeper Classic installation to Lansweeper Platform](/classic/docs/link-lansweeper-classic-with-lansweeper-platform), prerequisite checks confirm your installation is ready. The initial push usually succeeds once those checks pass, but sync errors can still happen. For example, if your Lansweeper server loses internet access after the checks pass and you've submitted your site details, the initial push fails.

## Before you begin

- Confirm your Lansweeper installation is up to date for full compatibility. See [Update Lansweeper Classic](/classic/docs/update-lansweeper-on-premises).
- Review any failures in the [prerequisite checks](/classic/docs/cloud-linking-requirements) and resolve them by following the instructions in the prerequisite check tooltip.

## Resolve initial push failure

1. If the push failed for a reason a retry can fix, the web console shows a **Retry initial push now** button in the **Troubleshooting** column of the **Configuration** > **Link with Cloud site** menu. For example, if your internet connection dropped after you submitted your link settings, select this button to retry.
2. If there's no retry button, or the sync still fails after a retry, remove the link and add it again. Select **Unlink from Cloud site**, wait for the unlink to finish, then select **Link with Cloud site** to try again.
3. If the push keeps failing and the cause is unclear, check these log files on your Lansweeper server:

The `sync_errorlog.txt` and `web_errorlog.txt` files only exist if errors occurred in your sync or web console.
  - `Program Files (x86)\Lansweeper\Service\errorlog.txt`
  - `Program Files (x86)\Lansweeper\Service\sync_errorlog.txt`
  - `Program Files (x86)\Lansweeper\Website\App_Data\web_errorlog.txt`

              Proxy connections need HTTP/2

              

Syncing with Lansweeper Platform sends an almost constant stream of data between your sync server and the cloud. Lansweeper only allows syncing through HTTP/2-enabled proxies. If your installation uses a proxy for outbound traffic, enable HTTP/2 or add an exception that bypasses the proxy for `edge.eu.lansweeper.com` or `edge.us.lansweeper.com`, depending on your region.