Pack_obj-Packing obj=Protocol=3.0|Command=VMSetup|Firmware=FGVMK6-FW-7.00-0157|SerialNumber=FGVM01TMYYYYYYYY|Connection=Internet|Address=z.z.z.z:0|Language=en-US|TimeZone=8|UpdateMethod=1|Uid=f2d7fc26af8a4b9c826f378ece503a01|VMPlatform=KVM
ssl_add_ftgd_hostname_check: Add hostname checking '' ssl_ctx_create_new_ex: SSL CTX is created ssl_ctx_use_builtin_store: Enable OCSP Stapling. ssl_ctx_use_builtin_store: Enable CRL checking.
ssl_ctx_use_builtin_store: Loaded Fortinet Trusted Certs _ssl_cert_ctx_load: Added cert /etc/cert/factory/root_Fortinet_Factory.cer, root ca Fortinet_CA, idx 0 (default) Upd_fds_load_default_server6-Resolve fds ipv6 address failed. Upd_fds_load_default_server-Resolve fds ip address OK. Now Fortigate would be able to get registered or update successfully: Re-run the command to register FortiGate to FortiCare or update the definition via FortiGuard: To change the MTU value of the interface, please refer to the following commands: Changing the MTU value would probably resolve the TLS connection establishment. One of the potential reasons is that the MTU on the WAN interface may have caused this issue. # upd_comm.c upd_comm_connect_fds-Failed SSL connect # upd_comm.c ssl_connect_fds-Poll event error:19 # upd_comm.c tcp_connect_fds-Proxy tunneling is disabled # upd_daemon.c do_update-Starting now UPDATE (final try) If the debug log shows the following, it highlights that FortiGate is having difficulty establishing a TLS handshake with FortiGuard servers, and the following error message can be seen: Initially check the connection to FortiGuard as below and the result could potentially show successful ping results:Ĭheck on the debug log to see what would be the potential cause:
This article describes the potential root cause of being unable to register a new FortiGate to FortiCare or update FortiGuard despite resolving of FortiGuard servers being successful.
0 kommentar(er)
