Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 14905 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Temporary TLS handshake timeouts

Jelle

We're experiencing temporary TLS handshake timeouts resulting in websites not loading. For example if we want to got to google.com we sometimes see that the browser is trying to do the handshake and after the specified timeout the webpage does not load. Most times it needs 3 or 4 reloads before the page gets loaded. It will work then for a certain time before it happens again. This can be seen with several websites. No specific time, no specific websites, just TLS handshake suddenly failing for some time.

We already had this issue with 17.0.5 and it did not change with 17.1.1.

A few days ago I checked MTU and MSS and changed it from 1500 to 1492 according to our WAN connections. I thought it got better but now it seems that the issue still persists.

Has anybody seen this before?



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to rfcat_vk

    This morning the issue became a major one as a lot of requests were failing at least the first time. So I rebooted the primary appliance and the auxiliary appliance took over. Guess what? The issue is not happening on the auxiliary (now primary) device although it is up since the installation of SFOS 17.1.1 like the other appliance.

    So why do the two device behave different although their uptime was the same? Could be an hardware issue or what is more likely that something is slowing down the appliance over time when it is primary in A-P mode.

    I'm going to check this during the next days. Maybe the issue can be seen on the other appliance too after it has been primary for some time.

Children