Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Host issues with DNS ip https - EAI_AGAIN and ECONNREFUSED #33

Closed
idkq opened this issue Jun 18, 2022 · 3 comments
Closed

Host issues with DNS ip https - EAI_AGAIN and ECONNREFUSED #33

idkq opened this issue Jun 18, 2022 · 3 comments

Comments

@idkq
Copy link

idkq commented Jun 18, 2022

Hi, I've been trying to setup this for a while now and I never get any errors but nothing happens when I update or add docs to the collection it was supposed to be indexing. How to troubleshoot the change in the document? What commands should I use?

The only log I can see is when running tail -f /var/log/typesense/typesense.log

I20220618 02:35:29.949776 28495 raft_server.h:60] Peer refresh succeeded!
I20220618 02:35:39.951146 28490 raft_server.cpp:531] Term: 5, last_index index: 18, committed_index: 18, known_applied_index: 18, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 44

Cloud logs return 0 logs.

My setup:

  • I have a fresh Ubuntu AWS Lightsail running typesense
  • port 8108 is open
  • https is on
  • health check returns ok.
  • Collection was created on the server
  • typesense_sync collection created

Questions:

  • Can we please expand the readme to include how to troubleshoot?
  • Can we please add to the readme examples of the config? I.e. do I need a forward slash for collections? Do I need the port on the server?

image

I am using this to test if a change in a doc creates any new document but It always return 0 documents.

curl -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
     -X GET \
    "https://EXAMPLE.com:8108/collections/service"
{"created_at":1655499258,"default_sorting_field":"","fields":[{"facet":false,"index":true,"infix":false,"locale":"","name":".*","optional":true,"sort":false,"type":"auto"}],"name":"service","num_documents":0,"symbols_to_index":[],"token_separators":[]}%       
@idkq idkq changed the title How to troubleshoot? I never get any error Host issues with DNS ip https - EAI_AGAIN and ECONNREFUSED Jun 18, 2022
@idkq
Copy link
Author

idkq commented Jun 18, 2022

Actually I was having issues navigating the Cloud Function log.

I'm getting two errors

If host is https://EXAMPLE.com I get this error:

EAI_AGAIN getaddrinfo EAI_AGAIN https

See
#16

If I omit https from host and add port (EXAMPLE.com:8108) I have:

ECONNREFUSED connect ECONNREFUSED x.x.x.x:443"

@jasonbosco
Copy link
Member

jasonbosco commented Jun 18, 2022

The extension only works on port 443, since Firebase makes calls out over the public internet.

So you'd only need to specify EXAMPLE.com in the host name field, and run Typesense on port 443 with an SSL certificate.

@idkq
Copy link
Author

idkq commented Jun 21, 2022

Changing the port from 8108 to 443 worked for me. Many thanks @jasonbosco

@idkq idkq closed this as completed Jun 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants