I discovered this error began occurring with version 2023 of the Web Screens.  It would appear to be the result of improved security on Sage's part.  The cause of the error for me was accessing the login screen from a different URL than that published in the underlying SSL certificate.  In version 2024, this error was improved further with an actual message being returned instead of "Undefined".  In version 2024, the error reads as: "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."

In version 2023, I could immediately work around the "undefined" error by accessing the site over port 80 http externally (this was via a secure VPN) until the problem with the external subdomain and SSL mismatch was rectified.  The cause may not be the same for you but if you're using an internally signed SSL and users are accessing the site using a different IP or hostname externally, it may be the cause.  You could try switching back to port 80 http briefly to test if the error goes away externally (perhaps do this after hours with production databases offline for security).

Cheers

I discovered this error began occurring with version 2023 of the Web Screens.  It would appear to be the result of improved security on Sage's part.  The cause of the error for me was accessing the login screen from a different URL than that published in the underlying SSL certificate.  In version 2024, this error was improved further with an actual message being returned instead of "Undefined".  In version 2024, the error reads as: "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."

In version 2023, I could immediately work around the "undefined" error by accessing the site over port 80 http externally (this was via a secure VPN) until the problem with the external subdomain and SSL mismatch was rectified.  The cause may not be the same for you but if you're using an internally signed SSL and users are accessing the site using a different IP or hostname externally, it may be the cause.  You could try switching back to port 80 http briefly to test if the error goes away externally (perhaps do this after hours with production databases offline for security).

Cheers

Thank you for the feedback.