Skip to content
  • There are no suggestions because the search field is empty.

How to Reconnect Webgility Desktop to QuickBooks POS After Moving to a New Server

This article helps Webgility Desktop users resolve connection issues between Webgility Desktop and QuickBooks Point of Sale that may occur after migrating POS to a new server and reinstalling Webgility Desktop. It provides step-by-step guidance to address common causes such as incorrect server configuration, missing settings, or disabled network ports, and restore proper integration.

Issue

After moving QuickBooks POS to a new server, you may see errors in Webgility Desktop when trying to connect to POS. Common causes include:

  • Incorrect server name or database details in Webgility Desktop
  • Missing configuration files after reinstall
  • Firewall or network port restrictions on the new server

Prerequisites

Before you begin, make sure you have:

  • Access to both the old and new servers
  • Administrator rights on both machines
  • Details or backups of your previous Webgility Desktop configuration

Troubleshooting Steps

1. Verify Installation

  • Confirm that both QuickBooks POS and Webgility Desktop are fully installed on the new server.
  • Make sure both applications are updated to the latest version.

2. Migrate Webgility Desktop Settings

  • On the old server, locate your Webgility Desktop configuration or settings folder.
  • Export or back up the settings using the Webgility Desktop migration documentation.
  • Move the files to the new server and import them to avoid having to reconfigure everything from scratch.

  1. Update Server Name and Database Connection
  • In Webgility Desktop, go to: Connections > Accounting/POS/ERP >  Edit Connection
  • Confirm the server name matches the new server’s hostname or IP address.
  • Update the POS database credentials if they changed during the migration (e.g., new usernames or passwords).

4. Enable Required Network Ports

  • Check the firewall settings on the new server to ensure the required ports are open.
  • For QuickBooks POS, commonly used ports include:
    • TCP 5636
    • Any custom ports defined during installation

  • To open a port on Windows:

    • Go to Control Panel > Windows Defender Firewall > Advanced Settings
    • Add a New Inbound Rule for the appropriate TCP ports

5. Test the Connection

  • In Webgility Desktop, return to the POS connection settings and click Test Connection.
  • If the connection fails:
    • Double-check the server name and spelling
    • Confirm user/database permissions
  1. Final Checks
Once the connection is successful, perform a test transaction in Webgility Desktop to verify that data flows correctly to QuickBooks POS.