How to disable TLS when TLS is being terminated by a TLS reverse proxy?

Support
, ,
1

Description

I want to run bare weaviate on its own, barebones.

I choose weaviate because it has the features I need, and it’s written in Go - so I knew the deployment would be very straightforward and easy (single binary, no crazy version or dependency issues).

I decided to download the release from GitHub Releases because, well, it’s there.

I did a quick weaviate –help and decided that I’d need to use --host and --port.

./weaviate --host 10.10.10.101 --port 3080

Then I immediately ran into the error “the required flags --tls-certificate and --tls-key were not specified”, but I already have a TLS Reverse Proxy handling SNI+ALPN, so I don’t need weaviate to handle any TLS for me.

How do I run it in the simplest possible way?

Server Setup Information

  • Weaviate Server Version: N/A
  • Deployment Method: GitHub Relases
  • Multi Node? Number of Running Nodes: N/A
  • Client Language and Version: N/A
  • Multitenancy?: N/A

Any additional Information

I would love to get a link to the server documentation.

I could find cloud setups and client setups, but I haven’t been able to find the simple “set these 3 flags and off you go” documentation anywhere.

2

Not totally sure if there is any documentation, but you can add `-–scheme
http` when starting the server. It’s what I use for my local developement :slight_smile: