Hey everyone :wave: Would anyone be able to help ...
# community-help
m
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
j
@michtio You'd have to setup A Records for each node's public IP address and that should pretty much be it
m
Without anything else? So nginx wouldn't be needed
Well of course not
Just maybe for the SSL on port 443, any config that needs to happen to let it run on 443?
j
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
m
Thank you @Jason Bosco 👍
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 🙂
@Jason Bosco is it actually possible to use nginx as front for Typesense? If yes, where should the entry point at?
j
@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.
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
m
Thanks @Jason Bosco, Kishore already helped me out in DM, got my Typesense cluster up and running with SSL certs 💪
🙌 1