-
Bug
-
Resolution: Done
-
Major
-
2.6.0.GA
-
False
-
False
-
Undefined
-
-
2 independent users report problems starting a workspace in this configuration. The error message received is "Server 'theia' in container 'theia-xyz' not available."
User B reports:
"I have tried with and without server.noProxyHosts set with same result. Proxy/cluster contains proxy/noProxy configuration and CA certificates used for ingress and api certificates."
User B environment(s):
OCP 4.6.8 on AWS or GCP. Using proxy and certificates signed by corporate private CA.
User B further comments:
"I have tried as well on a cluster in Azure without proxy and with ingress certificates from Let's Encrypt and everything works fine there."