Troubleshooting Typesense Launch with HTTPS Protocol via Docker
TLDR 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.
Sep 14, 2022 (13 months ago)
I'm using docker with these parameters:
docker run -p 8108:8108 -v/tmp/data:/data typesense/typesense:0.23.1 --data-dir /data --api-key=xyz --ssl-certificate=/etc/ssl/certs/nginx-selfsigned.crt --ssl-certificate-key=/etc/ssl/private/nginx-selfsigned.key --api-port=443
But I get the message "Bye." and nothing happens... this occurs when I attach the parameter: --ssl-certificate
Kishore Nallan01:42 PM
Kishore Nallan02:12 PM
SSL: no alternative certificate subject name matches target host name _*<IP ADDRESS>*_
I am generating the cert with openssl for the specific server IP, am I doing something wrong? i need to specify the port or something?
Kishore Nallan03:34 PM
Sep 15, 2022 (13 months ago)
Kishore Nallan12:37 PM
Indexed 2776 threads (79% resolved)
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.
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 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.
Typesense Certificate Error in Docker Compose
Suraj encountered an issue with typesense not finding SSL certificates in docker compose, even though certs were mounted successfully. After several suggestions by Jason, the issue was resolved by Suraj by mounting the correct folder in the docker compose file.
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.