Connection Refused Issue with Typesense and Nginx Reverse Proxy
TLDR Karthik experiences a connection refused problem with Typesense and Nginx reverse proxy. Jason helps troubleshoot, but the issue remains unresolved.
Jason
Fri, 17 Mar 2023 23:18:14 UTCIf you’re trying to connect to Typesense running on 8108, you don’t need to run it through nginx
Jason
Fri, 17 Mar 2023 23:18:41 UTCIt sounds like typesense server is not running based on the connection refused error
Jason
Fri, 17 Mar 2023 23:19:07 UTCDoes `px aux | grep typesense-server` give you any results?
Srini
Sat, 18 Mar 2023 00:22:58 UTCJason replying as Karthik left home; typesense is running. We are trying to configure the nextjs app on nodejs proxied by nginx and the app has a typesnse searchbar
Srini
Sat, 18 Mar 2023 00:27:03 UTCJason ● typesense-server.service - Typesense Server
Loaded: loaded (/etc/systemd/system/typesense-server.service; enabled; preset: enabled)
Active: active (running) since Sat 2023-03-18 00:20:35 UTC; 5min ago
Docs:
Jason
Sat, 18 Mar 2023 00:48:33 UTCCould you run and share the output of this: ```sudo netstat -nlp | grep :8108```
Jason
Sat, 18 Mar 2023 00:49:48 UTCCould you also share the output of the following: ```date ; tail -100 /var/log/typesense/typesense.log```
Jason
Sat, 18 Mar 2023 00:50:48 UTCAnd also this:
```curl
Srini
Sat, 18 Mar 2023 00:59:38 UTCJason lsof -i :8108
Srini
Sat, 18 Mar 2023 00:59:39 UTCCOMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME typesense 158688 root 23u IPv4 789450 0t0 TCP *:8108 (LISTEN)
Srini
Sat, 18 Mar 2023 01:00:31 UTC{"ok":true}
Jason
Sat, 18 Mar 2023 01:01:13 UTCOk so Typesense is running and is healthy
Jason
Sat, 18 Mar 2023 01:01:47 UTCFrom the very first message:
>
Jason
Sat, 18 Mar 2023 01:02:02 UTCAre you running on docker?
Srini
Sat, 18 Mar 2023 01:02:36 UTCno we are notu using docker
Srini
Sat, 18 Mar 2023 01:02:39 UTCsudo netstat -nlp | grep :8108 tcp 0 0 0.0.0.0:8108 0.0.0.0:* LISTEN 158688/typesense-se
Srini
Sat, 18 Mar 2023 01:03:12 UTCyou can access
Jason
Sat, 18 Mar 2023 01:04:45 UTCIt looks like the Typesense hostname is just configured as
Jason
Sat, 18 Mar 2023 01:05:06 UTCI see what you’re trying to do now
Jason
Sat, 18 Mar 2023 01:05:30 UTCYou probably want to have Typesense behind say `
Jason
Sat, 18 Mar 2023 01:06:14 UTCYou want something like this in your nginx config:
Jason
Sat, 18 Mar 2023 01:06:39 UTC```location /search {
rewrite /search/(.*) /$1 break;
proxy_pass
Srini
Sat, 18 Mar 2023 01:08:28 UTCI already did this
Srini
Sat, 18 Mar 2023 01:08:43 UTClocation / {
#try_files $uri $uri/ =404;
proxy_pass
Jason
Sat, 18 Mar 2023 01:11:17 UTCCould you post the last few logs from the nginx error log file?
Srini
Sat, 18 Mar 2023 01:11:18 UTCjust a note this works perfectly fine in local laptop it only happens in cloud wuth nginx reverse proxy
Jason
Sat, 18 Mar 2023 01:11:53 UTCI see a HTTP 500 thrown for that path, so should show some error in the nginx log file
Srini
Sat, 18 Mar 2023 01:13:16 UTC24.44.64.232 - - [18/Mar/2023:01:12:32 +0000] "GET /_next/static/webpack/webpack.7a7305f32c49b41c.hot-update.js HTTP/1.1" 200 858 "
Srini
Sat, 18 Mar 2023 01:13:27 UTCthat is from access.log
Jason
Sat, 18 Mar 2023 01:13:57 UTCYou want to look at error.log
Srini
Sat, 18 Mar 2023 01:14:09 UTCthis is from error.log
Srini
Sat, 18 Mar 2023 01:14:10 UTC2023/03/18 01:12:11 [error] 8671#8671: *26307 connect() failed (111: Connection refused) while connecting to upstream, client: 24.44.64.232, server:
Jason
Sat, 18 Mar 2023 01:15:25 UTCI don’t see any requests to multi_search here… Could you first visit the site, generate a multi_search request, and then post the lines from the logs?
Srini
Sat, 18 Mar 2023 01:15:25 UTCdo need to add upstream tag in nginx config?
Jason
Sat, 18 Mar 2023 01:16:01 UTCMy nginx knowledge might be outdated, but afaik, that shouldn’t be needed
Srini
Sat, 18 Mar 2023 01:16:45 UTCbtw Thank you so much for helping us on a Friday evening
Srini
Sat, 18 Mar 2023 01:17:00 UTCI really appreciate yoru help
Srini
Sat, 18 Mar 2023 01:17:19 UTCnothing is coming in error.log when id do the search
Jason
Sat, 18 Mar 2023 01:18:46 UTCIs something else in front of nginx that could be catching that request and throwing a 500?
Jason
Sat, 18 Mar 2023 01:19:21 UTCBecause the multi_search request I see generated by the frontend has to show up either in access log or error log
Jason
Sat, 18 Mar 2023 01:19:29 UTCif it doesn’t show up in either places, it’s not reaching this nginx server
Srini
Sat, 18 Mar 2023 01:20:10 UTCnothing is infront of nginx : the config is like this :--> nginx - nodejs nginx - typenses-adapter
Jason
Sat, 18 Mar 2023 01:20:32 UTCCould you try debug just this:
Jason
Sat, 18 Mar 2023 01:20:51 UTCsearch the logs for a POST request to multi_search
Srini
Sat, 18 Mar 2023 01:24:05 UTCI don;t think it is a nginx problem, it is somewhere in config of Nextjs and typsense adapter
Srini
Sat, 18 Mar 2023 01:32:15 UTCJason have a good night.
Typesense
Indexed 3051 threads
Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI
View in App
Karthik
Fri, 17 Mar 2023 23:07:00 UTCwe are running the following on ubuntu on vultr : nginx reverse proxy, nextjs apps on node on localhost:3000; typesense on localhost:8108; Here is my current nginx config; location / { #try_files $uri $uri/ =404; proxy_pass;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
} I an getting a connection refused with typsense; xhr.js?4381:210 POST net::ERR_CONNECTION_REFUSED I am assuming I should also add typesense to proxy_pass; is that correct? if so how do i add?Any help will be appreciated to resolve this issue