"Request timed out" for API call in Glide but working in Reqbin

[MattGlides]

I did see another post about this and would like to state that this API IS an https and it is a rest API. Currently I have all my data set up in a JSON template column:

The only header they require is Content-Type: application/json and as you can see I attached the above in my API call(the JSON template is the body):

However it is returning this error message:

Now I have no experience with reqbin but I went there, copy pasted exactly what is in my template JSON column into the content there. Added in the singluar header(content-type) and copy pasted the exact endpoint in my API… and it worked perfectly:

Has anyone ran into this issue before or have any idea what I could be doing wrong?

(Added note, nothing in my JSON template column is being replaced. I am sending the exact copy paste example they have given us)

[ThinhDinh]

I doubt this relates to CORS, but other than that I don’t know why it wouldn’t work, providing you have the correct setup and the response time of 1133 ms in the last screenshot.

Have you tried configuring that as an action opposed to a column?

[MattGlides]

Tried it, still didn’t. So I tried their schema, which is literally just a GET API call with one header. No body. Just an endpoint, via GET method, content-type:application/json. Once again, complete time-out. If I add it as a button action(watched Robert and Darren Humphries videos on that and it works the same as the column so I know thats correct too) the button just goes light for 30 seconds then dark again and nothing happened, i.e timed out. And once again if I literally just copy my endpoint into reqbin.com, and add that singluar header…

This is really frustrating so I added more of the endpoint in the ss, does the fact its a port mean thats why Glide is struggling?

[Darren_Murphy]

@MattGlides

This is really frustrating so I added more of the endpoint in the ss, does the fact its a port mean thats why Glide is struggling?

That’s quite possible. So it’s expecting HTTPS on port 501?
It might be that Glide enforces port 443 for HTTPS.

@DJP can probably answer that one.

(If you have access to webserver, you could test this by setting up a dummy endpoint, and then run a tcpdump on the ingress interface).

[MattGlides]

35501 are the last numbers after the : in that endpoint, not sure on the relevance but yes an answer would be appreciated. If Glide does enforce port 443, is that something the API could change on their end(to your knowledge I understand some differ). Basically will it still be possible to form a connection if this is the issue.

[Darren_Murphy]

Yes, anything that comes after the colon and the first forward slash is the port number.
443 is the default port for HTTPS, but it’s not uncommon for custom port numbers to be used.

I don’t know if Glide force 443 or not, that was just speculation. But it would explain the timeout.
If that is the case, then you’d either need to ask the provider if they can provide an endpoint that listens on 433, or hope that Glide might add support for custom ports.

Anyway, all speculation. Best to wait for a definitive answer.

[MattGlides]

Okay thanks, while I wait for a response can I ask: to your knowledge if Glide does enforce a 443(speculation) and the API keeps their custom port number is there any other way to connect if Glide doesn’t allow for custom ports(speculation)? So if the API won’t change and neither will Glide, would there be another way?

[Darren_Murphy]

Another option would be to setup a forwarding proxy server.

[DJP]

Hi, Matt! For something like this, we will need more information about your app, so our Engineering team can look into it.

Please follow these steps to open a Support ticket: Support | Glide Docs