You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are sitting behind a corporate firewall that will just let connections that are not allowed time out.
This causes some issues when our customers try to connect to services not allowed in the firewall because linkerd gives them a SSL_ERROR_SYSCALL (in curl) or some other seemingly SSL related error on their side when linkerd's outbound connection timeout hits.
Is there a way to configure linkerd so that outbound connection timeouts will actually show as e.g. a gateway timeout to the client?
The real problem here is that the error doesn't really hint at the problem (timeout/no firewall clearance) and people spent their time on debugging whether e.g. root CAs are present in their pods etc.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
We are sitting behind a corporate firewall that will just let connections that are not allowed time out.
This causes some issues when our customers try to connect to services not allowed in the firewall because linkerd gives them a SSL_ERROR_SYSCALL (in curl) or some other seemingly SSL related error on their side when linkerd's outbound connection timeout hits.
Is there a way to configure linkerd so that outbound connection timeouts will actually show as e.g. a gateway timeout to the client?
The real problem here is that the error doesn't really hint at the problem (timeout/no firewall clearance) and people spent their time on debugging whether e.g. root CAs are present in their pods etc.
Cheers!
Beta Was this translation helpful? Give feedback.
All reactions