IP weirdness with TS server:
when I start typesens...
# community-helpa
Alex K
04/08/2022, 9:39 AMIP weirdness with TS server:
when I start typesense specifying an IP / PORT like so:
--api-address 159.203.31.163 \
--api-port=80
but then I get this:
typesense TCP 10.20.0.5:8107 (LISTEN)
typesense TCP 159.203.31.163:80 (LISTEN)
and in the TS log I can see the 10.x IP being used, while there is nothing listening on that IP on port 80:
CURL failed. URL: http://10.20.0.5:80/health, Code: 7, strerror: Couldn't connect to server
k
Kishore Nallan
04/08/2022, 9:41 AMThere are two address configs. One for api http service which is configured via --api-address and the other is for the raft port that listens on 8107 -- this raft listener uses an internal interface only by default.
a
Alex K
04/08/2022, 9:42 AMok, but why does TS try to connect to port 80 for a health check on that internal IP?
k
Kishore Nallan
04/08/2022, 9:42 AMIt shouldn't.
Kishore Nallan
04/08/2022, 9:42 AMCheck the logs to see if there are any errors with api port binding.
Kishore Nallan
04/08/2022, 9:43 AMIf you have SSL configured you need to use https while curling.
a
Alex K
04/08/2022, 9:44 AMThis is not something I'm doing, I'm assuming TS does some selfcheck on the wrong IP/PORT: CURL failed. URL: http://10.20.0.5:80/health, Code: 7, strerror: Couldn't connect to server
k
Kishore Nallan
04/08/2022, 9:45 AMOh you see that in the logs?
a
Alex K
04/08/2022, 9:45 AMyup it's in the nohup error log
k
Kishore Nallan
04/08/2022, 9:46 AMAre you using clustering?
a
Alex K
04/08/2022, 9:46 AMnot in this case no.
Alex K
04/08/2022, 9:47 AMnohup ./typesense-server --data-dir=/home/alex/tsdata --api-key=$TYPESENSE_API_KEY --enable-cors \
--api-address 159.203.31.163 \
--api-port=80 \
--log-dir=/home/alex/tsdata/log
k
Kishore Nallan
04/08/2022, 9:47 AMCan you add a equals after --api-address flag?
a
Alex K
04/08/2022, 9:47 AMsure
Alex K
04/08/2022, 11:29 AMSo when I started version 23.rc47 it seemed to ignore the api-address line altogether and bind to * . I didn't see any of the healthcheck errors in the log, but also binding to * might explain that.
k
Kishore Nallan
04/08/2022, 11:35 AMOh okay, we did make one recent change related to this part. I will take a look.
a
Alex K
04/08/2022, 11:37 AMmy JS client had a issues connecting to rc47 too
k
Kishore Nallan
04/08/2022, 11:38 AMWe've other customers using rc47 though. Maybe they don't use custom API address.
Kishore Nallan
04/08/2022, 11:38 AMDo you have multiple public IPs? Otherwise binding to * is generally fine since you do intend to expose it to internet.
a
Alex K
04/08/2022, 11:58 AMSo when I remove the --api-address line then 23.RC47 also ignores --api-port=80 and binds to: *:8108
Alex K
04/08/2022, 12:07 PMApiCall.ts:203 Request #1649419591544: Request to Node 0 failed due to "undefined Network Error"
performRequest @ ApiCall.ts:203
ApiCall.ts:205 Request #1649419591544: Sleeping for 0.1s and then retrying request...
performRequest @ ApiCall.ts:205
localhost/multi_search?x-typesense-api-key=xyz:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
ApiCall.ts:203 Request #1649419591544: Request to Node 0 failed due to "undefined Network Error"
performRequest @ ApiCall.ts:203
ApiCall.ts:205 Request #1649419591544: Sleeping for 0.1s and then retrying request...
performRequest @ ApiCall.ts:205
localhost/multi_search?x-typesense-api-key=xyz:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
Alex K
04/08/2022, 12:08 PMbut curl connects just fine
k
Kishore Nallan
04/08/2022, 12:25 PMOk will look at this and get back to you.
Kishore Nallan
04/09/2022, 1:29 AMWe're indeed using the internal IP for an internal health call which happens after a snapshot. But for single node setup, this is not critical and should not affect the server ops.
If you just remove the api-address config, Typesense will listen on all interfaces or can also explicitly use:
Copy code
--api-address=0.0.0.0Kishore Nallan
04/09/2022, 2:08 AMThis is how Typesense has always been, so maybe you've never set this config directly before so didn't notice this problem? Despite that error, single node operations won't be anwyay affected.
a
Alex K
04/09/2022, 5:42 AMWell they are affected: My JS code which comes from your Ecommerce example is no longer able to connect to the single 23.RC47 node. And If I do remove the --api-address line from startup, --api-port=80 is ignored. so 23.RC47 is unable to have a port set unless an --api-address line is in the config
k
Kishore Nallan
04/09/2022, 5:46 AMI'm just trying this locally and removing api address has no impact on port. So very strange... Let me try again on a Linux box. Was trying on local mac.
a
Alex K
04/09/2022, 6:52 AMI'm thinking it also might be ignoring the --enable-cors switch as the error I get with RC47 is: Access to XMLHttpRequest at 'http://159.203.31.163/multi_search?x-typesense-api-key=xyz' from origin 'http://alex.pc-america.com:3010' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Alex K
04/09/2022, 6:53 AMSame code works fine with 22.2
Alex K
04/09/2022, 6:53 AMnohup ./typesense-server --data-dir=/home/alex/tsdata --api-key=$TYPESENSE_API_KEY --enable-cors \
--api-address=0.0.0.0 \
--api-port=80 \
--log-dir=/home/alex/tsdata/log
k
Kishore Nallan
04/09/2022, 7:16 AMOh right it might be a cors issue.
a
Alex K
04/09/2022, 7:18 AMI could try with a different 23.RC maybe?
Alex K
04/09/2022, 11:04 AMAlternatively is there a way to check if cors is enabled? like some sort of display current config command that can be issued to TS?
k
Kishore Nallan
04/09/2022, 12:10 PMThe response header should have access-control-allow-origin as *
I've been AFK so haven't been able to investigate yet, sorry. Will keep you posted.
a
Alex K
04/09/2022, 2:46 PMno rush 😉
k
Kishore Nallan
04/10/2022, 3:08 AMTurned out to be an annoying bug with the command line parser. People were trying to enable cors by send a true value, like
--enable-cors=true--enable-cors --api-address=0.0.0.0--enable-cors=true✅ 1