#community-help

Changing Path for Typesense Server Configuration

TLDR Karthik wanted to change the path in Typesense server config. Jason suggested updating the nodes and using Nginx reverse proxy for the desired configuration.

6mo

Join the chat

Mar 22, 2023 (6 months ago)

Photo of md5-b7a258bf917f26602c9d5efc88bfc6f5

Karthik

03:19 PM

Jason, Is there any way to change the path from this to <http://localhost:8108/multi_search?x-typesense-api-key=xyz> this <http://localhost:8108/typesense/multi_search?x-typesense-api-key=xyz>

import TypesenseInstantsearchAdapter from "typesense-instantsearch-adapter";

let TYPESENSE_SERVER_CONFIG = {
  apiKey: "xyz", 
  nodes: [
    {
      host: "localhost",
      port: 8108,
      protocol: "http",
    },
  ],
  connectionTimeoutSeconds: 1,
  numRetries: 8,
};

export const typesenseAdapter = new TypesenseInstantsearchAdapter({
  server: TYPESENSE_SERVER_CONFIG,
  additionalSearchParameters: {
    query_by: "CAS_ID,Synonyms,Molecular_Weight",
    queryByWeights: "4,2,2",
    numTypos: 3,
    typoTokensThreshold: 1,
  },
});

export const searchClient = typesenseAdapter.searchClient;

above code, I wrote in next.js - typesenseadapter.js

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

03:36 PM

You can update the nodes config to this:

nodes: [
    {
      host: "localhost",
      path: "/typesense",
      port: 8108,
      protocol: "http",
    },

Karthik

03:49 PM

after adding the prop path I am getting an error - 400 { "message": "Not Found"}

Jason

03:54 PM

Could you look at the browser’s network inspector and share the actual path being generated?

03:54

Jason

03:54 PM

Wait do you already have Typesense running behind <http://localhost:8108/typesense/> via a reverse proxy?

Karthik

03:59 PM

I am trying on my local system Linux, and also 8108 port is running on my system

Jason

04:00 PM

See our previous thread about first running Typesense on that path via a reverse proxy: https://typesense-community.slack.com/archives/C01P749MET0/p1679094420084709

04:00

Jason

04:00 PM

Only once you have that working, will changing the config in the adapter work

Karthik

04:01 PM

04:02

Karthik

04:02 PM

I will try to repopulate the data with new configuration using typesense npm

08:28

Karthik

08:28 PM

Jason how can I add a path to the typesense server configuration

Jason

08:57 PM

Typesense does not support this natively

08:57

Jason

08:57 PM

So it will only listen to the root path

08:57

Jason

08:57 PM

You have to put nginx in front of Typesense if you want to serve from a sub-path

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

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

Issues with Typesense Frontend Search Integration

Akash experienced issues integrating Typesense into their frontend search, particularly with their search box. Jason guided them to troubleshoot, eventually identifying the issue to be with react-instantsearch-dom and suggesting a downgrade to react 17, which resolved the issue.

11mo

Troubleshooting Typesense Hosting Issues on Google Cloud

Sachyya sought assistance on a Google Cloud Typesense hosting issue. Kishore Nallan helped identify a firewall rule problem and clarified how to configure settings, resolving the issue. They also advised Ahmet on synonym handling in the OSS version.

14mo

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