Troubleshooting Tip: Captive portal not reachable after FortiNAC upgrade: 'Service Unavailable'
| Description | This article describes an issue that may affect setups that are upgraded from firmware v9.x running in CentOS to firmware v7.x running in FortiNAC-OS. The captive portal is not reachable, the reason (error 503): 'Service Unavailable. The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.' |
| Scope | FortiNAC. |
| Solution | This issue is caused by the service not binding to the port (8009). This can be checked by running the following command from the CLI:
execute enter-shell $ netstat -an | grep 8009
If the line is missing, that means that the service is not listening on that port, and the portal page will not be reachable. This is caused by a configuration parameter that was used in older versions of FortiNAC and should not be used anymore.
The second check is done directly to the database by running the following command:
execute db-shell MariaDB [bsc]> select useNativeTransport from PAPacketTransportConfig;
If the output is showing the value '1', open a ticket with TAC support and reference this article.
This can be avoided by disabling the option 'Use Native Transport (experimental)' before proceeding with the migration. The details are shown below:
|
