I am using an ssl certificate and have a keystore on my production Basex instance. Are there extra steps needed to make an HTTPS request from a server to a basex server when those are in place?
On Thu, Sep 26, 2019 at 6:14 PM Marie Starck marie.compsci14@gmail.com wrote:
Hey Christian,
This error message is from doing it with the nodejs basex client. I get the same connection time out when doing an http or https request on 8984 and 8986 (non-ssl and ssl respectively).
Thank you,
Marie
On Thu, Sep 26, 2019 at 5:54 PM Christian Grün christian.gruen@gmail.com wrote:
Hi Marie,
SOCKET ERROR: { Error: connect ETIMEDOUT 159.89.126.125:1984
By default, the REST endpoints are available on port 8984.
Maybe this helps, Christian
Hi Marie,
Sorry for not giving you any further response. Maybe it helps to simplify the test setting: Can you access REST without node.js? What may be the easiest setup that could be reproduced? Or have you already found a solution?
Cheers, Christian
On Thu, Sep 26, 2019 at 8:26 AM Marie Starck marie.compsci14@gmail.com wrote:
I am using an ssl certificate and have a keystore on my production Basex instance. Are there extra steps needed to make an HTTPS request from a server to a basex server when those are in place?
On Thu, Sep 26, 2019 at 6:14 PM Marie Starck marie.compsci14@gmail.com wrote:
Hey Christian,
This error message is from doing it with the nodejs basex client. I get the same connection time out when doing an http or https request on 8984 and 8986 (non-ssl and ssl respectively).
Thank you,
Marie
On Thu, Sep 26, 2019 at 5:54 PM Christian Grün christian.gruen@gmail.com wrote:
Hi Marie,
SOCKET ERROR: { Error: connect ETIMEDOUT 159.89.126.125:1984
By default, the REST endpoints are available on port 8984.
Maybe this helps, Christian
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Marie Starck