#community-help

Troubleshooting AWS Server Setup with Typesense

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

25mo

Join the chat

Aug 14, 2021 (25 months ago)

Photo of md5-d9ca032e3941589aafa8433269974f96

Ankit

01:33 PM

A question for those who created their own server. I was trying to setup my own server in AWS and then use the api calls. I installed typesense, got it running, and called from my local (using the IP and port) but no response. Then I installed nginx, set it up for reverse proxy and port 8108 but no response when using curl from local.

Here is the curl command I am using: http://<<Server IP>>:8108/health

Also checked the inbound rules for server. They are fine, and nginx default page loads. Do I need to install something else?

One other thing, the docs said
> By default, Typesense will start on port 8108, and the installation will generate a random API key, which you can view/change from the configuration file at /etc/typesense/typesense-server.ini
The file is not created, nor the API key is generated. Am I doing something wrong?

When I installed it on local the curl call for health check works fine.

Aug 15, 2021 (25 months ago)

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

03:29 AM

Typesense uses a production-ready evented HTTP library so you don't have to use nginx.

> The file is not created, nor the API key is generated.
This is true only for DEB and RPM installations. How did you install Typesense?

Please post your typesense config INI file so I can see if there is something missing.

Ankit

12:47 PM

> How did you install Typesense?
Linux binary. (tar.gx file acc to documentation).
The ini file is not generated either. There is nothing in /etc as the typesense folder is not created (does it require root permissions, I did not use that)

Kishore Nallan

12:50 PM

Use a DEB or RPM, only those generates those files. The tar gz is not an installer so contains only the binary.

Ankit

12:58 PM

ok. After that I can call typesense api directly right? (without having to install nginx and substituting IP for localhost)

Kishore Nallan

12:58 PM

Yes. The INI file will be created. If you want you can change the port to default HTTPS port of 443.

Ankit

02:05 PM

It works now. Thanks a lot for your help

Kishore Nallan

02:05 PM

:yw:

Typesense

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

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Resolving Connection Issues on Ubuntu 21.10

Philipe faced a problem with TypeSense running on Ubuntu 21.10. After troubleshooting, Jason and Kishore Nallan suggested a binary to solve the compatibility issue, which resolved the issue.

21mo

Connection Refused Issue with Typesense and Nginx Reverse Proxy

Karthik experiences a connection refused problem with Typesense and Nginx reverse proxy. Jason helps troubleshoot, but the issue remains unresolved.

6mo

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.

16mo

Typesense Search Functionality Issue on CentOS Client Server

Shabber is facing an issue with Typesense search functionality on a CentOS client server. The curl request works, but not from JS. The issue remains unresolved, and Shabber will request the public IP of the server and enable port 8108.

4mo

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

17mo