Connection timeout
Thursday, 26 September 2019 · 4 messages · last reply 1 Oct 2019
MS
Marie Starck26 Sep 2019 06:42 #
Been debugging this for the past couple of days and I am a bit stumped. I am doing a simple get REST request to my BaseX server from a node server and I keep getting a connection timeout error. I also tried the basex node client and I get the same error message.
All of this works fine on localhost and what's even weirder is that I can access the BaseX rest endpoint through my browser just fine. Any ideas? I have SSL installed on my BaseX server. Could that be the issue?
SOCKET ERROR: { Error: connect ETIMEDOUT 159.89.126.125:1984 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1173:14) errno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
address: '159.89.126.125',
port: 1984 }
Thank you for any help you can give me,
Marie
CG
Christian Grün26 Sep 2019 07:54 #
Hi Marie,
SOCKET ERROR: { Error: connect ETIMEDOUT 159.89.126.125:1984
Quoted text · Marie Starck · 1 line
>
By default, the REST endpoints are available on port 8984.
Maybe this helps,
Christian
MS
Marie Starck26 Sep 2019 08:26 #
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?
Quoted text · Marie Starck · 27 lines
On Thu, Sep 26, 2019 at 6:14 PM Marie Starck <marie.compsci14 at 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 at 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 >> >> >>
CG
Christian Grün1 Oct 2019 14:53 #
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
Quoted text · Marie Starck · 27 lines
On Thu, Sep 26, 2019 at 8:26 AM Marie Starck <marie.compsci14 at 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 at 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 at 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 >>> >>>
Written for BaseX 9.2. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery