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

How to solve "Remove name could not be resolved" and performance issues in Webgility Desktop

This article helps Webgility Desktop users address two common issues in the Webgility Desktop: "Remote name could not be resolved" errors, Slow performance or application freezing. These problems may be caused by DNS resolution issues, network conflicts, or interference from multiple antivirus programs.

1. Remote Name Resolution Error

Common Causes

  • DNS resolution failure

  • Network connectivity issues

  • Server unavailability

  • Typos in domain names

  • Conflicts from antivirus/firewall configurations

Fix Steps

💡 Perform the following steps on the computer where Webgility is installed (usually the server machine).

Step-by-step Instructions:

  1. Open Command Prompt as Administrator:

    • Right-click Command Prompt

    • Select Run as Administrator

  2. Type the following command and press Enter:

    bash
    CopyEdit
    ipconfig /flushdns

  3. Wait for the confirmation message:
    "Successfully flushed the DNS Resolver Cache."

  4. Navigate to the following path:

    makefile
    CopyEdit
    C:\Windows\System32\drivers\etc

  5. Locate the file named: hosts

  6. Right-click on the hosts file → Select Open with > Notepad

  7. Scroll to the bottom of the file and add this line:

     
    CopyEdit
    34.215.85.106 portal.webgility.com

  8. Save the file and close Notepad.

  9. Relaunch Webgility Desktop.

2. Performance Troubleshooting

If Webgility is slow or freezing:

Check System Resources:

  1. Open Task Manager (Ctrl + Shift + Esc).

  2. Monitor the following under the Processes tab:

    • CPU usage

    • Memory usage

    • Disk activity

    • Presence of multiple antivirus programs

🛠️ Multiple antivirus or firewall software may conflict with Webgility and degrade performance. Consider disabling or whitelisting Webgility in these tools.