Skip to main content
gsharma
Staff
Staff
April 8, 2026

Technical Tip: FortiADC disconnected from FortiAnalyzer

Description This article describes the reason for FortiADC disconnecting from FortiAnalyzer.
Scope FortiADC, FortiAnalyzer.
Solution

There can be a scenario where, after upgrading FortiADC, it is unable to connect to FortiAnalyzer.

 

To verify further, take debugs:

 

diagnose debug module miglogd oftp_detail set

diagnose debug enable

 

If the logs show something similar to this:

 

date=2026-03-09 time=13:19:44 device_id=FADVMS***** log_id=0005002005 type=event subtype=slb pri=notice vd=hosted msg_id=220828219 policy="web****" group="none" member="none" attrtype="none" attrname="none" action="ssl" status="failure" logdesc="SLB SSL Handshake" msg="Client 10.10.10.1 failed to establish SSL connection with VS web***** of ip 10.10.20.2 : error:0A0000EA:SSL routines::callback failed

(__ssl_load_cert : 384) Failed in ctx get cert
(__ssl_cert_ctx_free : 237) Done
(__ssl_ctx_create_new : 558) Failed in loading cert(s)
(ssl_ctx_free : 262) Done

 

Then, proceed to the CLI of FortiADC, log in with the admin account, and run the command below to check if the certs are there:

 

fn ls /etc/snca

 

If this shows empty output, then this is the only reason for this connectivity failure.

 

Expected output:

 

fn ls /etc/snca
snca1.cer snca1.key snca2.cer snca2.key

 

If certs are there and still the SSL connection is failing, then continue troubleshooting using the below article:
Troubleshooting Tip: How to troubleshoot connectivity between FortiAnalyzer and FortiADC

Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT