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

Resolving SSL Security Errors During Webgility Login via Server Reboot

This article helps Webgility Desktop users troubleshoot SSL security errors that occur during login. It covers initial troubleshooting steps and explains how rebooting the main server machine can resolve persistent SSL issues.

Overview

An SSL security error may occur when attempting to log in to Webgility Desktop. In some cases, initial troubleshooting steps may not resolve the issue. This article explains how the problem can be resolved when a server reboot is required.

Troubleshooting Steps

If you encounter an SSL error while logging into Webgility Desktop, the following steps may help:

  • Restart SQL Server services.

If this steps do not resolve the issue, continue with the resolution steps below.

Final Resolution Step

If the error persists, a full server reboot may be necessary. This was the solution in a previous case where a complete reboot by the hosting provider (e.g., Ace Cloud) resolved the issue successfully. No additional actions were required after the reboot.

When a Server Reboot May Be Needed

A full server reboot is recommended in the following scenarios:

  • The SSL error continues after upgrading the database and restarting SQL services.

  • Changes to the SQL connection string or provider have no effect.

  • The error message indicates issues related to SSL/TLS configuration on the system level.

Suggested Process for Resolution

To resolve this type of SSL error, follow this process:

  1. Note the exact error message encountered during login.

  2. Perform these steps:

    • Upgrade the Webgility database.

    • Restart SQL Server services.

  3. If the issue is still unresolved:

    • Review recent changes to the hosting or server environment.

    • Contact your hosting or server administrator.

    • Request a full server reboot (not just an application or service restart).

Additional Notes

SSL login errors can sometimes be caused by broader system or network issues beyond the application's configuration. It is important to ensure that your server is in good health and that the network connection is stable—especially if using a hosted or cloud-based server environment.

Reference Links : click here