Skip to content

[Bug] DBQnA: blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource #2081

Open
@hualongfeng

Description

@hualongfeng

Priority

P2-High

OS type

Ubuntu

Hardware type

Xeon-SPR

Installation method

  • Pull docker images from hub.docker.com
  • Build docker images from source
  • Other
  • N/A

Deploy method

  • Docker
  • Docker Compose
  • Kubernetes Helm Charts
  • Kubernetes GMC
  • Other
  • N/A

Running nodes

Single Node

What's the version?

version: v1.3 opea/text2sql-react-ui rebuild based on main branch

Description

I run DBQna in a vagrant virtual machine. The UI needs to export port 5174 to host. Postgress, as a database, also needs to export port 5442 to host. These two ports are reasonable, but I didn't expect that port 9090 of text2sql-service also needs to be exported. We obviously use nginx in the UI service, so why can't we hide the text2sql UI in the backend like Chatqna? Using it directly on the frontend makes me unable to use DBQna normally.

Image

Reproduce steps

Running all service in a virtual machine and export port to host, then access the UI in another machine.

Please don't run web, dbqna service on same machine. Thanks

Raw log

Attachments

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingwontfixThis will not be worked on

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions