Getting Timeout error after updating from 3.7.300.29 to 3.7.301 and later versions

[Dattatreya-27]

Describe the bug

my project is working for me in local and working with older versions on my server too but from version 3.7.301.0 it starts failing with the same code for S3 buckets , is it related to weather S3 bucket is on premise or not ?
getting the below error .

Amazon.Runtime.AmazonServiceException: A WebException with status ConnectFailure was thrown. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it

Expected Behavior

should be successfully able to fetch event data from S3 bucket

Current Behavior

My request is getting timeout or retry getting exceed as it is not able to connect

Reproduction Steps

updating awssdk.core to version 3.7.301 or above

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

AWSSDK.CORE 3.7.301

Targeted .NET Platform

.NET 6

Operating System and version

Windows 10

[dscpinheiro]

Do you have reproduction code you can share?

Version 3.7.301 of AWSSDK.Core added support for http_proxy and https_proxy (https://github.com/aws/aws-sdk-net/blob/main/changelogs/SDK.CHANGELOG.2024.md#377200-2024-01-04-1956-utc), so if those environment variables are set they'll be automatically picked up by the SDK.

[Dattatreya-27]

Sharing the code library might not be possible but yea I will check the above release notes , please share any other suggestions you might have as the same code works in local with higher versions but only causes problem when on server might be some relation to weather server is on premise or not .

[dscpinheiro]

Another thing you can try is verbose logging, that should give you more insights on what the SDK is trying to do:

AWSConfigs.LoggingConfig.LogTo = LoggingOptions.Console;
AWSConfigs.LoggingConfig.LogMetricsFormat = LogMetricsFormatOption.JSON;
AWSConfigs.LoggingConfig.LogResponses = ResponseLoggingOption.Always;
AWSConfigs.LoggingConfig.LogMetrics = true;

using var s3Client = new AmazonS3Client();
await s3Client.ListBucketsAsync();

[github-actions]

This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

[Dattatreya-27]

 <proxy proxyaddress="ProxyAddress" bypassonlocal="True" usesystemdefault="False" />
    <bypasslist>
        #{ProxyBypassList}
    </bypasslist>
    

this is kind of how we are adding proxy in our system I found that when above proxy is added amazon client dose not have ServiceId populated which is why connection is getting refused 

Do I need to change how I am adding proxy?

@dscpinheiro can you help

[Dattatreya-27]

After further investigation I have found that we are using caddy and following is the error we are getting when trying to fetch object from S3 bucket :-
WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Maybe this will help troubleshoot the error

[dscpinheiro]

By Caddy do you mean https://github.com/caddyserver/caddy?

If you still see the error when communicating with AWS directly let us know, but if that works you'll have to reach out to Caddy (there's unfortunately not much the SDK can do here).

[github-actions]

This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.