[Bug]ChatQnA browser interface requires http link, creates a friction point for developers

[arun-gupta]

Priority

Undecided

OS type

Ubuntu

Hardware type

Xeon-GNR

Installation method

• [X] Pull docker images from hub.docker.com
• [ ] Build docker images from source

Deploy method

• [X] Docker compose
• [ ] Docker
• [ ] Kubernetes
• [ ] Helm

Running nodes

Single Node

What's the version?

latest

Description

Started ChatQnA example in IBM Cloud and trying to access the UI interface. By default, typing the :5173 resolves to https://:5173. Chrome shows the following warning message

Developers may not feel very safe about this environment. Either we should secure the example or provide a warning message in the documentation.

Reproduce steps

Follow the steps here to deploy anywhere https://github.com/opea-project/GenAIExamples/tree/main/ChatQnA

Raw log

No response

[mkbhanda]

To support HTTPS we need to deploy a certificate to the UI service which opens up issues a self signed certificate (which will pop up a message like do you trust XYZ certificate) or get a valid certificate signed through a chain by a certificate authority etc.

For development purposes one typically sets up a port forward, so you can reach the UI service without complaints using local host http://localhost:5173/

at which point we should get something like