Hi
I have two virtual services say one for domain a.example.com and another for b.example.com.
When i add sslConfig for one it works completely fine. But when i add it for both am not able to access my service i get
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to a.example.com:443
Using the same sslConfig for both virtual services. Does anyone have any idea what could be the issue here.
I tried adding sniDomains with values a.example.com in one and b.example.com in the second one, but error is shown. When i remove sslConfig from one virtual service it works again.
Steps to reproduce the bug
I am using the same certificate for both my virtual services
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Gloo Edge Version
1.9.x
Kubernetes Version
1.20.x
Describe the bug
Hi I have two virtual services say one for domain a.example.com and another for b.example.com. When i add sslConfig for one it works completely fine. But when i add it for both am not able to access my service i get
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to a.example.com:443
Using the same sslConfig for both virtual services. Does anyone have any idea what could be the issue here. I tried adding sniDomains with values
a.example.com
in one andb.example.com
in the second one, but error is shown. When i remove sslConfig from one virtual service it works again.Steps to reproduce the bug
I am using the same certificate for both my virtual services
Expected Behavior
I should be able to access my services across https in both virtual services.
Additional Context
Output of
glooctl check
Could be possibly relate to this https://github.com/solo-io/gloo/issues/2534 but i cant seem to find a workaround