Ok… how are you deploying the Tyk Gateway ?
Two things I am suspicious of:
1 - You are launching Gateway using Docker and not mounting the cert
2 - The cert’s cname is not matching the tyk gateway’s and it’s ignoring it
3 - an invalid cert
Is your cert self signed or CA signed
I have launched gateway on EC2 instance and certificate is CA signed and I am using it on my load balancer as well which is working fine.
I tried with self signed and i am able to access API’s. It seems something i am missing in bundling CA signed certificate since it is chain of certificates includes root/intermediate/end-user certs and it may require all the certs to identify and validate certificate.