| Description | This article describes a scenario where, upon upgrade, the portal produces an 'Internal Error 500' after the login page. The URL for the page with the 500 error will end with the "SMAAuthenticate.jsp" script, and logins will not succeed. |
| Scope | 9.x |
| Solution |
A reboot of the FortiNAC appliance will rebuild the Tomcat/Java cache and resolve the error:
|
