HTTP connection failing since Saturday with bad request but no changes made to vnet or logic app

Gareth T 30 Reputation points
2023-06-26T10:30:33.15+00:00

I have a standard logic app which is posting to an internal web service and has had no issues since its creation earlier this year. Over the weekend this started giving this error: "Http request failed as there is an error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond." Our on prem gateway is functioning and our VNET appears to be connected correctly. I ran a diagnostics on the vnet and got the attached errors.

The internal web service is working when tested from postman whilst connected to our vpn.

I'm not sure what else to check, any help would be appreciated.

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,555 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Ryan Hill 30,281 Reputation points Microsoft Employee Moderator
    2023-06-26T20:30:58.6533333+00:00

    Hi @Gareth T

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that the question author cannot accept their own answer, they can only accept answers by others, I'll repost your solution in case you'd like to Accept the answer.

    You have a logic app that posts to an internal web service. The app started to experience connectivity issues. You verified the gateway and VNET configuration had not changed.

    You determined that the issue was related to Border Gateway Protocol (BGP) routing issue.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.