Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 1271 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 610 [details]
1) Get a job for a company that restricts the crap out of everything on their network.
2) Run MonoDevelop, Tools->Add-in Manager
3) Go to Gallery, click refresh icon
Exception thrown about proxy requiring logon info. (See attached screen cap)
1) Better error message.
2) A place I can enter proxy logon information
3) It should just work, as both IE and Firefox seem to "detect" these settings off the network.
Hmm, I can't reproduce step 1 ;-)
Anyway, on Windows, MD runs on .NET, and it should be using .NET's default proxy settings, which IIRC are loaded from IE.
You may be able to fix this by setting the default proxy to use default credentials. You can do it in MonoDevelop.exe.config, or you could fix it for *all* .NET apps in your system's machine.config. See http://stackoverflow.com/questions/914306 for some details.
Yup! This fixes the problem. I'll attach a work-around .config file to the bug.
If you believe MonoDevelop should either somehow set this behavior at runtime, or ship with this .config file, then feel free to use this bug to track; if everything is behaving as expected, feel free to close.
Created attachment 613 [details]
Config file to work-around the proxy issue
This will fix the issue:
<defaultProxy enabled="true" useDefaultCredentials="true">
I would argue this is a bug in the .NET default machine.config, but if we can work around it then we should.