#community-help

Issues with Accessing TypeSense Cloud Server from Iran

TLDR Stephano reported his colleague in Iran had difficulty accessing the TypeSense cloud server. Jason helped with troubleshooting, speculating it could be due to US sanctions. Some connectivity achieved through VPN, but issues persisted.

29mo

Join the chat

Jun 14, 2021 (29 months ago)

Photo of md5-1b5a9819eb84d9342bdcd7da73258779

Stephano

07:02 PM

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" }

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

07:10 PM

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.

Stephano

07:11 PM

He refreshed multiple times and it finally worked

07:11

Stephano

07:11 PM

We use a postgres and node server both hosted on AWS which do not pose problems

07:11

Stephano

07:11 PM

He’s said that it is very slow

07:12

Stephano

07:12 PM

And keeps getting This site can't be reached

Jason

07:12 PM

Oh I see, interesting

Stephano

07:12 PM

Like I said we already host the rest of our backend on aws 🙂

Jason

07:12 PM

Which AWS region are you hosted in though?

Stephano

07:13 PM

eu-west-1

07:13

Stephano

07:13 PM

Typesense is the same:

Single Region
Ireland

Jason

07:14 PM

Hmmm. Could you try (temporarily) connecting to the Typesense Cloud node via it's public IP address?

Stephano

07:14 PM

07:14

Stephano

07:14 PM

Where do I find the IP address?

Jason

07:17 PM

dig <http://xxx-1.a1.typesense.net|xxx-1.a1.typesense.net>

07:18

Jason

07:18 PM

Once you get the IP address, could you do this:

curl -vvvv -k

and paste the output?

Stephano

07:30 PM

~! ❯ 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):

07:31

Stephano

07:31 PM

07:31

Stephano

07:31 PM

When he turns on his VPN it works

07:34

Stephano

07:34 PM

This does not work for him in the browser with VPN off:

https://18.202.252.126/health

Jason

07:37 PM

Does the curl command hang after that "Client hello" line?

Stephano

07:37 PM

Yeah

Jason

07:38 PM

Hmmm, where is the VPN based out of? Ireland as well?

07:40

Jason

07:40 PM

Also, do you use a VPN to connect to your node app and DB as well?

Stephano

07:54 PM

No I don’t think he did

Jason

07:58 PM

Could you do this: traceroute 18.202.252.126

08:00

Jason

08:00 PM

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

Stephano

08:09 PM

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
*

08:15

Stephano

08:15 PM

It makes no sense because the other services work great

Jason

08:50 PM

Could you try the solutions listed here: https://apple.stackexchange.com/questions/114115/network-stops-working-with-cant-assign-requested-address

Typesense

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

Indexed 2779 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.

7mo

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.

23mo

Protecting Typesense Queries from DOS Attacks

Juri sought advice on securing typesense queries. Jason suggested use of Cloudflare for DOS attack protection and explained how to create user-specific API keys for data authorization. Ricardo endorsed Cloudflare for protection.

31mo

Deploying to Fly.io via Dockerfile

andrew asks how to launch to Fly.io with Docker. Jason guides them on the environment setup, specifically mentioning persistent VMs, and approves andrew's Dockerfile setup.

8mo

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

19mo