@azure/app-configuration problem using VPN

[Makoehle]

• Package Name: @azure/app-configuration
• Package Version: 1.8.0
• Operating system: WSL2 Ubuntu
• nodejs
  • version: 22.13.0
• browser
  • name/version:
• typescript
  • version: 5.7.2
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://learn.microsoft.com

Describe the bug
Having a VPN activated when I read from App Config I receive an error. See context. This doesn't happen without VPN. In order to exclude VPN from the possible list of failures I did the same with using @azure/storage-blob.

So as soon as a VPN is deactivated both the @azure/app-configuration and
@azure/storage-blob works as expected. But as soon as the VPN is activated
@azure/app-configuration fails to read the configuration settings.

Do you have suggestions how to solve this problem? When doing remote work this might be a blocker.

To Reproduce

Expected behavior
The error added under Additional context doesn't occur.

Additional context

azure:core-rest-pipeline retryPolicy:info Retry 3: Maximum retries reached. Returning the last received response, or throwing the last received error.
RestError:  
 {
  "name": "RestError",
  "code": "ETIMEDOUT",
  "request": {
    "url": "https://<your-app-conf>.azconfig.io/kv?api-version=2023-11-01",
    "headers": {
      "accept": "application/vnd.microsoft.appconfig.kvset+json, application/problem+json",
      "accept-encoding": "gzip,deflate",
      "user-agent": "azsdk-js-app-configuration/1.8.0 core-rest-pipeline/1.18.1 Node/22.13.0 OS/(x64-Linux-5.15.167.4-microsoft-standard-WSL2)",
      "x-ms-client-request-id": "9898ac84-dab8-48fb-b5b7-e4a744376303",
      "authorization": "REDACTED"
    },
    "method": "GET",
    "timeout": 0,
    "disableKeepAlive": false,
    "streamResponseStatusCodes": {},
    "withCredentials": false,
    "tracingOptions": {
      "tracingContext": {
        "_contextMap": {}
      }
    },
    "requestId": "9898ac84-dab8-48fb-b5b7-e4a744376303",
    "allowInsecureConnection": false,
    "enableBrowserStreams": false
  }
}

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @avanigupta.

[xirzec]

ETIMEDOUT generally means the socket was never opened to the remote server. As far as I'm aware the @azure/app-configuration package doesn't do anything special with respect to its HTTP pipeline that should affect this.

If it's the service rejecting traffic from your VPN address, you could try filing a support ticket with the service here: https://azure.microsoft.com/en-us/support/create-ticket