Auto-detect proxy settings not working

I installed Arduino IDE on our IT class computers. We have also configured our corporate proxy so Arduino is allowed to download libraries. Now Arduino is set to auto-detect proxy settings by default which would be fine. But we still get the "Error downloading https://downloads.arduino.cc/libraries/library_index.json".
If we configure the proxy manually it works. It also still works if we then switch back to auto-detect.
We do not have any other problems with other software regarding auto-detecting proxy and windows is also set to automatic.
Since the proxy settings are located in the userprofile and we have an environment where a lot of different users log on to that pc it is very difficult for us to configure this all manually.

Windows 10.0.16299
Arduino 1.8.10

IDE 1.8.10 has a lot of issues.
This may or may not be one of them.
Might I suggest roll back to 1.8.9 to test further ?

Bob.

Hi Bob

Thank you for your response.

I have installed the 1.8.9 Version on one client and i got the same problem.

If the proxy has already been set to allow properly elsewhere in the system / network then it may be that the setting should remain at the default with the boxes for network empty.

That it seems to forget from one moment to the next would indicate a setting at the backend that an IT department may need to fix.

Also the locations for the Arduino components need to also be allowed through.
Additional security such as antivirus and similar can also cause additional issues and very slow responses.

Add the Arduino directories to your antivirus / anti malware / other security exclusions.
So that would be at least two of the following.
C:\Program Files (x86)\Arduino
C:\Users\yourname\AppData\Local\Arduino15 depends on IDE
C:\Users\yourname\AppData\Roaming\Arduino15 depends on IDE
If you have your sketches set up in a different location it’s also worth adding that directory to the exclusions also.
Additionally if you also use the online IDE “CREATE” the following directories.
C:\Users\yourname\AppData\Roaming\ArduinoCreateAgent
C:\Users\yourname\AppData.arduino-create
If you have installed to a different drive swap the drive letter as needed.
If you also have an unzipped IDE installed that path should also be added to exclusions

ballscrewbob:
If the proxy has already been set to allow properly elsewhere in the system / network then it may be that the setting should remain at the default with the boxes for network empty.

We configured our proxy so downloading from "https://downloads.arduino.cc/" is possible. We tested this by setting our proxy manually in Arduino since we couldn't even see any blocks before in our proxy. So our configuration on our proxy is correct and should not interfere with anything we set in Arduino.
The Arduino default proxy setting is set to auto-detect without any boxes filled. We would prefer to keep it like that so we dont have to make any changes in everyones userprofile.

ballscrewbob:
That it seems to forget from one moment to the next would indicate a setting at the backend that an IT department may need to fix.

What do you mean it seems to forget? The Problem is that Arduino is not able to auto-detect the proxy settings while any other software like chrome has no problems to do so by auto-detect.

Antivirus also does not seem to be the problem since I can download libraries if I set the proxy manually.

I may have misread your first post.
Thought it seemed to forget in the same session ?

"Error downloading https://downloads.arduino.cc/libraries/library_index.json" has come up a few times recently now I think about it.

There seems to be a few methods to fix it (not always guaranteed).

You may want to try the more recent ones.
I know its a bit of a kitchen sink approach but about the best I can offer at this time.

Bob.

There was a bug in previous IDE versions where the proxy settings in the IDE's preferences were not properly handled:

However, that was supposed to be fixed in Arduino IDE 1.8.10, so I'm skeptical it's the cause of your problem. However, it might be worth noting if you're rolled back to 1.8.9, since the bug did still exist on that version.

Stoffi's bug report: