The remote server returned an error: (407) Proxy Authentication Required

Question

I'm getting this error when I call a web service:

"The remote server returned an error: (407) Proxy Authentication Required".

I get the general idea and I can get the code to work by adding

myProxy.Credentials = NetworkCredential("user", "password", "domain");

or by using DefaultCredentials in code. My problem is that the call to the web service works in production without this.

It seems like there is a non code solution involving Machine.config, but what is it? At the moment I can't get to the production box's machine.config file to see what that looks like. I tried updating my machine.config as follows, but I still get the 407 error.

<system.net>
    <defaultProxy enabled="true" useDefaultCredentials="true">
        <bypasslist>
            <clear />
        </bypasslist>
        <proxy proxyaddress="myproxy:9000"
               usesystemdefault="false"
               bypassonlocal="true"
               autoDetect="False" />
    </defaultProxy>
</system.net>

Davie

Answer 1

Just add this to config

<system.net>
    <defaultProxy useDefaultCredentials="true" >
    </defaultProxy>
</system.net>

Coleman

For those interested, this was exactly what I needed inside a NetSuite console / web services application from (what seems to be) a firewall / proxy constraint. – Rattlehead

Best answer, make it a configuration detail not a code problem. – Araldo

This still works in Asp.net core 2.0. I had to add a web.config file purely to handle this. – Bionomics

Mine is a C# console application working with AWS SDK to access S3 buckets. Add this to my app.config in my console application solved the issue – Waistcoat

Answer 2

In following code, we don't need to hard code the credentials.

service.Proxy = WebRequest.DefaultWebProxy;
service.Credentials = System.Net.CredentialCache.DefaultCredentials; ;
service.Proxy.Credentials = System.Net.CredentialCache.DefaultCredentials;

Chapbook

This worked perfect for me. If you find yourself not wanting to hardcode you username and password try this option first. – Allergic

Thanks that worked. However, are there security risks with doing it this way vs. the method shown by mehmet emin? With adding network credentials? Or would using network credentials give more permissions, and introduce a security risk? – Mock

@Mock Only problem with 'Mehmet Emin' code is hard-coding of credentials. In real worlds, password is changed every month due to security threats, so either make them configurable in config file. so it's always good to follow my stuff or I like Seckin way also. – Chapbook

Worked as expected. Thanks – Modular

@kucluk You have created object of service proxy, so put this code before calling any method of service. – Chapbook

Answer 3

Check with your firewall expert. They open the firewall for PROD servers so there is no need to use the Proxy.

Thanks your tip helped me solve my problem:

Had to to set the Credentials in two locations to get past the 407 error:

HttpWebRequest webRequest = WebRequest.Create(uirTradeStream) as HttpWebRequest;
webRequest.Proxy = WebRequest.DefaultWebProxy;
webRequest.Credentials = new NetworkCredential("user", "password", "domain");
webRequest.Proxy.Credentials = new NetworkCredential("user", "password", "domain");

and voila!

Shoebill

uirTradeStream ? – Canicula

Answer 4

Probably the machine or web.config in prod has the settings in the configuration; you probably won't need the proxy tag.

<system.net>
    <defaultProxy useDefaultCredentials="true" >
        <proxy usesystemdefault="False"
               proxyaddress="http://<ProxyLocation>:<port>"
               bypassonlocal="True"
               autoDetect="False" />
    </defaultProxy>
</system.net>

Juliannajulianne

Thanks, I tried this and I still get the "(407) Proxy Authentication Required" error. Does adding the section you list stop the error for you? The only thing that works for sure on my local box is to set the myProxy.Credentials property in code. – Davie

Answer 5

HttpWebRequest webRequest = WebRequest.Create(uirTradeStream) as HttpWebRequest;

webRequest.Proxy = WebRequest.DefaultWebProxy;

webRequest.Credentials = new NetworkCredential("user", "password");

webRequest.Proxy.Credentials = new NetworkCredential("user", "password");

It is successful.

Eurypterid

uirTradeStream ? – Canicula

hi using this code but it not working at webRequest.Proxy = WebRequest.DefaultWebProxy; and getting an exception: (407) Proxy Authentication Required. please help – Tamatave

Answer 6

Thought of writing this answer as nothing worked from above & you don't want to specify proxy location.

If you're using httpClient then consider this.

HttpClientHandler handler = new HttpClientHandler();

IWebProxy proxy = WebRequest.GetSystemWebProxy();
proxy.Credentials = CredentialCache.DefaultCredentials;
handler.Proxy = proxy;

var client = new HttpClient(handler);
// your next steps...

And if you're using HttpWebRequest:

HttpWebRequest request = (HttpWebRequest)WebRequest.Create(uri + _endpoint);

IWebProxy proxy = WebRequest.GetSystemWebProxy();
proxy.Credentials = CredentialCache.DefaultCredentials;
request.Proxy = proxy;

Kind referencce: https://medium.com/@siriphonnot/the-remote-server-returned-an-error-407-proxy-authentication-required-86ae489e401b

Sieracki

Answer 7

I had a similar proxy related problem. In my case it was enough to add:

webRequest.Proxy.Credentials = new NetworkCredential("user", "password", "domain");

Trifle