This issue can occur after performing an SCG upgrade, where the interface becomes inaccessible and displays a general server error message. The problem may appear immediately after the update and can affect access to the SCG web interface until corrective steps are taken.

This issue can occur due to API route changes in the new SCG version while the browser continues using cached JavaScript bundles referencing outdated routes. Additionally, custom configurations, such as certificates, may not persist after the update and must be reapplied manually.

Step 1: Clear Browser Cache

1. Clear the browser cache to remove any old, cached JS bundles:
   • Open your browser's settings.
   • Clear cached data (especially JavaScript files).
2. Reload the SCG interface to see if the issue is resolved.

Step 2: Reapply Certificate and Custom Configurations (if clearing cache does not work)

1. Check the SCG configuration after the update:
   • During the update, some configurations (like SSL certificates) may be lost.
   • Manually reapply any custom changes, including the certificate configuration.
2. Follow the documented process for adding certificates back, as described on uDocs.
3. After adding certificates or making any configuration changes, restart the SCG webserver:
   • Use the terminal session where the update was performed to restart the webserver.
   • This ensures that the new configuration takes effect.

After upgrading Scout Cloud Gateway (SCG) to a newer version (e.g., via scg_1.2409…deb), you may encounter a “General Server error” when accessing the SCG interface.

The browser cache may cause routing issues after upgrading, so clearing it is essential. Custom configurations, including SSL certificates, must be manually reapplied after the upgrade. Always restart the SCG webserver after modifying its configuration to ensure changes take effect.