Technical Tip: Log from FortiCloud source shows no results due to connection timeout

Description

This article discusses when the log is uploaded to the FortiCloud server and when no log result is shown on FortiGate when the log source is set to FortiCloud.

Scope

FortiGate.

Solution

1. Ensure the connection to the FortiCloud server is established.

For version 7.2.3 and below:

diagnose test application miglogd 20
Home log server:
    Address: 172.16.95.92:514
Alternative log server:
    Address: 172.16.95.26:514
    oftp status: established        <-----
Debug zone info:
    Server IP:      172.16.95.92
    Server port:    514
    Server status:  up
    Log quota:      102400MB
    Log used:       673MB
    Daily volume:   20480MB
    FDS arch pause: 0
fams archive pause: 0

For version 7.2.4 and above:

diagnose test application fgtlogd 20

2. If the connection is established, it is possible to set a longer connection timeout as below:

    

config log fortiguard setting
    set conn-timeout {integer}
end

FortiGate Cloud connection timeout in seconds.   

Minimum value: 1
Maximum value: 3600
Default value: 10

Related documents:
log fortiguard setting
Log-related diagnose commands