https://typesense.org logo
Join Slack
Powered by
My colleague in Iran cannot access the TypeSense c...
# community-help
s
My colleague in Iran cannot access the TypeSense cloud server. Via a https:// url, his browser hangs on a 
/health
request where as mine returns 
{ ok: "true" }
j
We're using AWS for Typesense Cloud, and AWS being a US-company, it looks like they might be blocking access to AWS resources from US-sanctioned countries (like Iran). Typesense is also a US-based entity and so we need to comply with those restrictions as well.
s
He refreshed multiple times and it finally worked
We use a postgres and node server both hosted on AWS which do not pose problems
He’s said that it is very slow
And keeps getting 
This site can't be reached
j
Oh I see, interesting
s
Like I said we already host the rest of our backend on aws 🙂
j
Which AWS region are you hosted in though?
s
eu-west-1
Typesense is the same:
Copy code
Single Region
Ireland
j
Hmmm. Could you try (temporarily) connecting to the Typesense Cloud node via it's public IP address?
s
Ok
Where do I find the IP address?
j
dig <http://xxx-1.a1.typesense.net|xxx-1.a1.typesense.net>
Once you get the IP address, could you do this:
Copy code
curl -vvvv -k <https://ip/health>
and paste the output?
s
Copy code
~! ❯ curl -vvvv -k <https://18.202.252.126/health>            0.24s ~
*  Trying 18.202.252.126...
* TCP_NODELAY set
* Connected to 18.202.252.126 (18.202.252.126) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/cert.pem
 CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
message has been deleted
When he turns on his VPN it works
This does not work for him in the browser with VPN off:
Copy code
<https://18.202.252.126/health>
j
Does the curl command hang after that "Client hello" line?
s
Yeah
j
Hmmm, where is the VPN based out of? Ireland as well?
Also, do you use a VPN to connect to your node app and DB as well?
s
No I don’t think he did
j
Could you do this: 
traceroute 18.202.252.126
Basically there's something that's blocking or slowing down connections between his network and AWS. We've only added financial-level controls on our side for Iranian users per legal requirements. So if there's a network level block, it's either coming from AWS or some Internet Service Provider between his network and the AWS network
s
Without VPN: 8 traceroute: wrote 18.202.252.126 52 chars, ret=-1  *traceroute: sendto: Can’t assign requested address traceroute: wrote 18.202.252.126 52 chars, ret=-1  *traceroute: sendto: Can’t assign requested address traceroute: wrote 18.202.252.126 52 chars, ret=-1  *
It makes no sense because the other services work great
j
Open in Slack
PreviousNext
Powered by