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

How to Resolve eBay Product Sync Issues Related to Localhost and Antivirus Conflicts in Webgility Desktop

This article helps Webgility Desktop users resolve product synchronization issues with the eBay sales channel in Webgility Desktop, especially when errors involve localhost connections (e.g., localhost:33387), manual syncs show no error messages, or antivirus and network settings disrupt the sync. It provides step-by-step guidance to address problems typically caused by local system configurations, security software interference, or certificate-related issues.

Initial Assessment – Information to Verify

  • Review which SKUs are not syncing with the eBay sales channel.

  • Attempt to reproduce the issue and take note of the exact steps followed.

  • Perform a manual sync and observe whether any on-screen feedback or error messages appear.

  • Look for any error popups or logs that mention URLs like localhost:33387.

  • Check if there have been any recent changes to your network, antivirus, firewall, or other security software that may affect connectivity.

 Check Integration Setup

    • Go to Connections > Sales Channel > Manage Sales Channel in Webgility Desktop.

    • Confirm that the eBay sales channel connection is active and properly configured.

    • Verify sync settings and account permissions meet eBay’s integration requirements.

Diagnosing Connection Issues

1. Localhost and Port Errors

Errors involving localhost:33387 usually indicate:

  • The local Webgility integration client is not running.

  • Antivirus or firewall software is blocking access to local ports.

  • Loopback (localhost) configuration is corrupted or disabled.

2. Antivirus and Security Software Interference

  • Some antivirus/firewall applications may block non-standard ports or flag Webgility's self-signed certificates.

  • This can prevent communication between the local client and browser or eBay’s API.

Recommended Actions:

  • Temporarily disable antivirus/firewall for testing.

  • Add application and port exceptions (e.g., port 33387).

  • Review security software logs for blocked activity or quarantined items.

Resolution Steps

1. Re-establish the eBay Integration Connection

  • Run the eBay sales channel setup on a clean system (ideally unaffected by previous antivirus blocks).

  • Go to Connections > Sales Channel > Manage Sales Channel in Webgility Desktop.

  • Click the Edit option in the Action column next to your eBay sales channel.

  • Click Connect to eBay to start the reauthorization process using the new OAuth flow.

  • A browser window will open—log in using your eBay admin account credentials.

  • After signing in, click I Agree to grant Webgility access to your eBay account.

  • Once you see the confirmation message, close the browser and return to Webgility.

  • Click Continue to complete the connection.

2. Verify Network & Localhost Configuration

  • Ensure loopback (127.0.0.1) is mapped correctly:

    • Use ping 127.0.0.1 from the Command Prompt to validate.

    • Use tools like telnet 127.0.0.1 33387 to test port accessibility.

  • Add exclusions in security software for:

    • Webgility Desktop and its services.

    • Port 33387 and other required localhost communication ports.

Post-Resolution Steps

  • Manually sync affected SKUs to confirm no errors persist.

  • If you're planning a server migration or database transfer, make sure to reauthorize the sales channel after the move to ensure continued integration.

Additional Notes

  • Future sync issues may arise if local network policies or certificates expire.

  • You should document your certificate renewal timelines and schedule regular updates to prevent future integration issues.

  • Always review sync logs after changes to confirm stability.