-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Timeout with Node Version <= 16 #118
Comments
I had all kinds of nonsense trying to set up a self hosted instance on a vps. Changing the port in the config file to port 80 and the same in the client fixed the issues for me. |
@Enragedsaturday you are right, the only solution i could find was to set the config on port 80, but in order to worker you need to NOT specify the port. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I set up my own self hosted typesense instance on a vps. Now when I use typesense-js with node version 16 or less I will always get a timeout. If I use Node 17 everything works fine. I guess it has to do something with my server setup or dns setup, since everything works fine when I start a local docker container. When I check the health endpoint I can curl it just fine.
Does anyone else had this issue and knows what to do?
The text was updated successfully, but these errors were encountered: