Webhooks working from server, but not from terminals

[JuiceyBrucey]

7.2.1.0
SR 16
I am updating inventory on JIWA directly on the server, and webhooks are coming through no problem. But when office staff update inventory from one of their computers, the webhook is not sent.
I have checked all other computers and they are all running:
7.2.1.0
SR 16
All of them can access: http://10.0.0.110:808/ and the metadata comes up no problem. (Not sure if that is relevant)
JIWA sends the webhooks to the website webhook page and records the webhook content immediately. So if the webhook is sent, I will be able to see it in the website admin immediately. But they are only being sent when I am logged into the server and updating inventory from there.

Not sure why some terminals are working, and others are not.
Any suggestions?

[Scott.Pearce]

What is the value in System Settings->System Configuration->REST API->HostURL? This should be a value that all clients can reach.

[Mike.Sheen]

What you are describing indicates that the clients cannot reach the configured WebhooksHostURL in your System Settings -> REST API tab.

Make sure you've read the Webhooks docs page.

[JuiceyBrucey]

thank you for the replies.
The WebhooksHostURL has been set to http://10.0.0.110:808/.
I dont know why as it does not point to my API or website at all.
This works on some computers and not others.
Is that the issue?

[Mike.Sheen]

The WebhooksHostURL has been set to http://10.0.0.110:808/.
I dont know why as it does not point to my API or website at all.
This works on some computers and not others.
Is that the issue?

Have you verified that http://10.0.0.110:808/ is reachable from the problem machines? Verify by opening a browser on the problem machines and visiting http://10.0.0.110:808/

[JuiceyBrucey]

Yes all can reach http://10.0.0.110:808/
Cheers

[Mike.Sheen]

Yes all can reach http://10.0.0.110:808/
Cheers

Ok, so look in the table SY_WebHookMessage - if clients cannot reach the Jiwa API, they will insert directly into the table SY_WebHookMessage with Status of 0 - are you seeing entries like that?

If so, then join those to the SY_WebhookMessageResponse table - this should show a HTTPCode and Message.

[JuiceyBrucey]

In the SY_WebHookMessage table, all of the status values are either 1 or 2.
When joining tables, there are some that have a status of 404 and a Body value of '', but the latest ones are all http:200 with a Body value of JSON object strings.
good to know these records are there BTW. Did not know about these.
Cheers

[Mike.Sheen]

In the SY_WebHookMessage table, all of the status values are either 1 or 2.
When joining tables, there are some that have a status of 404 and a Body value of '', but the latest ones are all http:200 with a Body value of JSON object strings.
good to know these records are there BTW. Did not know about these.
Cheers

So all good, then? You have enough to work it out from here, right?

[JuiceyBrucey]

Being able to see the webhook messages has been very helpful.
We have narrowed it down to one computer that is not sending webhooks. All the others are fine.
So I am inserting or editing an inventory item, and then checking the SY_WebHookMessage table for a new entry, but there is none.
That is where we are up to so far.
Cheers