Technical Tip: Troubleshooting Captive Portal page not building or rendering

[cmaheu]

Description
This article provides general troubleshooting steps when the Captive Portal page is not accessible by any client.

Scope
FortiNAC all versions

Solution

1) Verify httpd service is running.  In appliance CLI type

service httpd status

If httpd is not running, check the following logs for errors

/bsc/logs/messages

/bsc/logs/apache/error_log

If /var/log/messages file shows the following message:
httpd:  SSLCertificateFile: file '/bsc/siteConfiguration/apache_ssl/server.crt' does not exist or is empty

Confirm the Portal Target has SSL certificate installed. 
In Administration UI, navigate to System > Settings > Security > Certificate Management

If missing certificate in the Portal target, install one.  Refer to SSL Certificate Installation document for instructions.

2) Verify tomcat-portal is running

In appliance CLI type

service tomcat-portal status

If tomcat-portal is not running, check the following logs for errors

/bsc/logs/tomcat-portal/catalina.out

3) Ensure SSL certificate installed in Portal Certificate Target is valid.

     In Administration UI, navigate to System > Settings > Security > Certificate Management

If expired, install new certificate.  Refer to SSL Certificate Installation document for instructions.

4) Verify Portal certificate has all intermediate certificates installed.  For instructions, see related KB article below.

5) Verify Allowed domains required to allow for certificate validation are in Allowed Domains List.  For detail, see related KB article below (Captive Portal page secured with SSL certificate not building or slow to build).

Contact Support for additional assistance.

Related Articles

Technical Note: Identify missing SSL certificates via administration UI

Technical Note: Captive Portal page secured with SSL certificate not building or slow to build