#community-help

Misunderstanding Typesense and H2O Proxies

TLDR Daniel was confused about using H2O as a reverse proxy with Typesense. Jason clarified that H2O is not mandatory and that Typesense can be directly exposed to public traffic. Daniel decided to continue using NGINX.

22mo

Join the chat

Nov 17, 2021 (22 months ago)

Photo of md5-3e862430ae06b87120e3640d3f9f8061

Daniel

01:16 AM

Is a requirement to use H2O as the reverse proxy?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

01:17 AM

H2O is the http library we're using within Typesense. Out of curiosity, may I know where you read this as a requirement?

01:18

Jason

01:18 AM

In any case, in general, you don't need to run Typesense behind a reverse proxy. H2O which is baked into Typesense is a production-grade http server and can be exposed to public traffic

Daniel

01:18 AM

https://typesense.org/docs/guide/running-in-production.html#production-best-practices

Jason

01:19 AM

Are you referring to this line: Typesense comes built-in with a high performance HTTP server (opens new window)that is used by likes of Fastly (opens new window)in their edge servers at scale. So Typesense can be directly exposed to incoming public-facing internet traffic, without the need to place it behind another web server like Nginx / Apache or your backend API.

I don't see any other direct mentions of H2O

Daniel

01:19 AM

Yeah

01:19

Daniel

01:19 AM

But now I get it

Jason

01:20 AM

Was the wording confusing? Can we reword it better in some way?

Daniel

01:20 AM

I mean, I don't have any experience with H2O, do you have any examples exposing Typesense?

Jason

01:21 AM

You don't have to use H2O, that's a low-level detail inside of Typesense

Daniel

01:21 AM

No, it wasn't. It's really just me not reading very well

01:21

Daniel

01:21 AM

I'm not a native English speaker, so I may have misunderstood the paragraph

Jason

01:22 AM

Sometimes, people might want to put Typesense behind nginx - for eg, if you want to have Typesense be served behind a /sub-path

01:22

Jason

01:22 AM

If that's not needed, there's no additional setup needed

Daniel

01:22 AM

I'll stick with NGINX then haha, thanks 😃

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Typesense Setup with Reverse Proxy in Production

Suraj asked best practices for setting up Typesense in a production environment without exposing port 8108, and Kishore Nallan suggested using a reverse proxy behind nginx or Apache, as in the provided video.

3mo

Automating Letsencrypt and Using Nginx with Typesense

Sreekanth asked about automating Letsencrypt and using nginx as a reverse proxy with Typesense. Jason suggested handling Letsencrypt auto-renewal outside Typesense and clarified that nginx is not necessary unless more fine-grained control over routing is needed.

3mo

Connection Refused Issue with Typesense and Nginx Reverse Proxy

Karthik experiences a connection refused problem with Typesense and Nginx reverse proxy. Jason helps troubleshoot, but the issue remains unresolved.

6mo

Setting up DNS Records for Typesense Servers and SSL Configuration

michtio needed assistance in setting up DNS records for Typesense servers in AWS and configuring SSL. Jason shared steps on how to set up A Records and fetch an SSL cert for HTTPS on port 443. The user later solved his issue with Jason's help.

16mo

Changing Path for Typesense Server Configuration

Karthik wanted to change the path in Typesense server config. Jason suggested updating the nodes and using Nginx reverse proxy for the desired configuration.

6mo