#community-help

Setting up DNS Records for Typesense Servers and SSL Configuration

TLDR 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.

19mo

Join the chat

May 27, 2022 (19 months ago)

Photo of md5-68e2637c7df7044e63075bd8ec098420

michtio

08:14 AM

Hey everyone 👋

Would anyone be able to help me out how to setup a DNS records for the Typesense servers?
Would love to give our spun up clusters their own DNS records that can resolve the search results.

It’s spun up on AWS FYI, and DNS will be resolved through CloudFlare most likely

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

02:47 PM

michtio You'd have to setup A Records for each node's public IP address and that should pretty much be it

michtio

03:36 PM

Without anything else? So nginx wouldn't be needed

03:36

michtio

03:36 PM

Well of course not

03:36

michtio

03:36 PM

Just maybe for the SSL on port 443, any config that needs to happen to let it run on 443?

Jason

03:54 PM

You don't need nginx. You'd need to just get an SSL cert and point Typesense at it, to run HTTPS on port 443

03:55

Jason

03:55 PM

This guide has more details: https://typesense.org/docs/guide/running-in-production.html#configuration

May 30, 2022 (19 months ago)

michtio

07:15 AM

Thank you Jason 👍

09:02

michtio

09:02 AM

Reading that guide --> h2o HTTP server doesn’t need anything to be set-up like sites-available/sites-enable to point the domain name through to the correct server? I’ll see how it behaves with laravel-forge and Let’s Encrypt setup 🙂

02:19

michtio

02:19 PM

Jason is it actually possible to use nginx as front for Typesense? If yes, where should the entry point at?

Jason

03:19 PM

michtio h2o is an HTTP library that's built into Typesense, and doesn't have the concept of sites available / sites enabled. You don't need to configure a hostname inside of Typesense. You'd need to setup a DNS record with your hostname, pointing to the server IP that's running Typesense, and then get an SSL cert for that hostname.

03:19

Jason

03:19 PM

https://typesense-community.slack.com/archives/C01P749MET0/p1653920380745419?thread_ts=1653639281.045879&cid=C01P749MET0

Yes. You would set it to proxy calls to port 8108 on Typesense, which is Typesense's default HTTP port

michtio

03:20 PM

Thanks Jason, Kishore already helped me out in DM, got my Typesense cluster up and running with SSL certs 💪

Typesense

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

Indexed 3011 threads (79% resolved)

Join Our Community

Similar Threads

Troubleshooting Typesense and Firestore Connection

Carter had trouble connecting Typesense and Firestore. After troubleshooting with Jason, the issue was identified to be SSL cert setup, and resolved through setting-up ngrok tunnel for local-hosting.

15mo

Troubleshooting Typesense Launch with HTTPS Protocol via Docker

Gines struggled to launch Typesense with HTTPS, initially failing to mount the certificate directory in Docker. Even after addressing this, Gines hit an SSL error, to which Kishore Nallan confirmed that an actual hostname, not an IP address, was needed.

15mo

Setting Up and Accessing Remote Typesense Instance.

Kyle had trouble accessing a Typesense instance remotely. Jason helped them realize the solution lies in server configuration, opened ports, and necessary SSL certificates for individual sub-domains along with enabling CORS.

16mo

Configuring Docker-hosted Typesense with Let's Encrypt SSL Certificates

Ian asked for help with setting up SSL certificates in a Docker-hosted Typesense. Jason provided suggestions but the issue remains unresolved due to port conflict.

8mo

Troubleshooting AWS Server Setup with Typesense

Ankit faced issues setting up AWS server with Typesense. Kishore Nallan clarified the installation methods and suggested to use DEB or RPM instead, which resolved Ankit's issue.

29mo