Configuring CORS Settings for Whitelisting Domains
TLDR Fulvio needed help to configure CORS settings to whitelist specific domains. Jason clarified it's not currently supported, but suggested starting the docker container with
--enable-cors and reading the documentation.
Jul 26, 2021 (28 months ago)
*are whitelisted at the moment. Are you looking to whitelist only certain domains?
--enable-corscommand line arg when starting the docker container?
We don't support narrowing down the list at the moment. Could you open a Github issue about this?
Indexed 2779 threads (79% resolved)
Configuring CORS in Typesense Using Docker
Fulvio asked how to configure CORS. Jason recommended adding a `--enable-cors` flag, even when using Docker.
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.
Docker Compose Issue with Connecting Server and Typesense
Priyank couldn't connect their server with typesense through Docker compose. After troubleshooting with Kishore Nallan and WL, user discovered that they needed to specify the IP address of the typesense service in their client configuration.
Resolving CORS-related Issues with Typesense Server
Edson experienced typesense-related CORS issues, which Jason solved by advising to add the `--enable-cors` flag during the startup of the typesense server. The difference in how typesense instantsearch adapter works was also clarified.
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.