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.
Nov 17, 2021 (22 months ago)
I don't see any other direct mentions of H2O
Indexed 2764 threads (79% resolved)
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.
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.
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.
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.
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.