Setting Up and Accessing Remote Typesense Instance.
TLDR 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.
3
Sep 02, 2022 (14 months ago)
Kyle
03:37 PMcurl <http://localhost:8108/health>
while in my docker console and get back a status {"ok":true}
but I'm not sure how to access it remotely. It's hosted on a DigitalOcean droplet with it's own IP address but when I try to ping that ip it times out.Jason
03:57 PMJason
03:58 PMKyle
04:10 PMKyle
04:35 PMKyle
04:38 PM1
Jason
04:39 PMKyle
04:41 PM1
Kyle
07:01 PM<http://typesense.mywebsite.com|typesense.mywebsite.com>
I would assume I would just create and A Record for my DNS settings for the subdomain.What things do I need to configure on the server side? I figured enabling cors and setting the cors domains would link it externally but I'm still not getting a response when I ping the health.
Jason
07:16 PMJason
07:17 PMKyle
07:29 PMCurrently hosting through firebase.
Jason
09:32 PM1
Typesense
Indexed 2786 threads (79% resolved)
Similar Threads
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.
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.
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.
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.
Server IP Address and Port Issues with Typesense
Alex encountered problems with Typesense server configuration when setting IP and port using --api-address and --api-port, facing additional problems with CORS and version inequities. Kishore Nallan addressed each point, ultimately finding a bug with the command line parser affecting subsequent commands. The advised workaround was to use `--enable-cors=true`.