Closed prabhu0376 closed 2 years ago
Happening with all endpoints is interesting. My first guess would be firewall issues from the machine - are you able to connect to the same endpoint URLs using curl on the Tableau Server machine?
@jacalata Yes. CURL works. It is now confirmed that its a bug with Tableau Server App not honouring proxy settings with few of the features. A new one where it not works is Slack Integration too. Hopefully, Tableau should come up with a fix soon.
Hi Team,
I have set up Tableau Webhook that sends a JSON payload to webhook.site. Setting up of the webhook is successful. However, when attempted to Test the webhook, it gives the following response of unable to connect to the url "https://xxxx" with status 408 in the Responde Body.
From the webhook logs we see this: webhooks: INFO com.tableau.extensibility.webhooks.responder.http.HttpPostHookUtil - Sending message to https://some-internal-service/: webhooks: INFO com.tableau.extensibility.webhooks.responder.http.HttpPostHookSender - IOException on posting
We have Tableau Server 2020.3.3 and server machines are behind PROXY. The server machines do have access to webhook.site. What we have observed is that, when we Test the webhook from Postman it runs for 5 seconds and immediately after that. we get the response as mentioned (408-Unable to reach the URL). Could this be a time out issue from tableau side as we see the standard connect timeout default settings as 5 seconds and read timeout as 3 seconds? The certificates aren't Self Signed either.
webhooks.user_agent: TableauWebhooks/1.0 webhooks.http.timeout.connect: 5000 webhooks.http.timeout.read: 3000
The issue is happening with all the endpoints . Azure, GCP as well as webhook.site.