Skip to main content
AEK
SuperUser
SuperUser
May 4, 2025
Question

Sometimes can't access docs.fortinet.com

  • May 4, 2025
  • 2 replies
  • 1198 views

Hi community members

 

I noticed from time to time docs.fortinet.com is not accessible and I get the below error message.

 

 

Ftnt_eof_err.png

From CLI:

 

$ ping docs.fortinet.com
PING docs.fortinet.com.geo.fortinet.net (149.5.234.138) 56(84) bytes of data.
64 bytes from 149.5.234.138 (149.5.234.138): icmp_seq=1 ttl=46 time=51.0 ms
64 bytes from 149.5.234.138 (149.5.234.138): icmp_seq=2 ttl=46 time=43.4 ms
64 bytes from 149.5.234.138 (149.5.234.138): icmp_seq=3 ttl=46 time=57.1 ms
64 bytes from 149.5.234.138 (149.5.234.138): icmp_seq=4 ttl=46 time=43.0 ms

--- docs.fortinet.com.geo.fortinet.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 42.972/48.625/57.136/5.852 ms


$ wget https://docs.fortinet.com/document/fortigate/7.6.2/administration-guide/704939/vrrp-virtual-macs
--2025-05-04 09:43:02-- https://docs.fortinet.com/document/fortigate/7.6.2/administration-guide/704939/vrrp-virtual-macs
Resolving docs.fortinet.com (docs.fortinet.com)... 149.5.234.138
Connecting to docs.fortinet.com (docs.fortinet.com)|149.5.234.138|:443... connected.
OpenSSL: error:0A000126:SSL routines::unexpected eof while reading
Unable to establish SSL connection.

 

Anyone had the same issue?

2 replies

Atul_S
Staff & Editor
Staff & Editor
May 4, 2025

Hi AEK,

 

The error seems to be related to TLS handshake at the client end. Have you encountered the same issue while using diff browsers? Are you using proxy for your outbound Internet connection?

 

Thanks,

AEK
SuperUser
AEKAuthor
SuperUser
May 5, 2025

Hi Atul

Thanks for your response.

At the time when the issue occurs, I tested with other browsers but same result.

You see on the output even wget gives an error.

I'm not using proxy.

AEK
AEK
SuperUser
AEKAuthor
SuperUser
November 23, 2025

Hello @Atul_S 

The issue reappeared suddenly just now, and it was working fine just before.

It is the same from Chrome and Firefox. Here are screenshots from both.

 

ftnt1.pngftnt2.pngftnt3.png

 

The issue has been fixed within about 5 to 10 minutes, without any intervention.

AEK