Community
Participate
Working Groups
I'm accessing the web using a proxy that requires authentication. If the method I connect to the network with is set to "native" if I try to do a "Help/Check for updates" I get a "No updates found" almost immediately. And the info that trying to access the network wasn't possible because the "proxy requires authentification". Which it does. If I set the network connection to "manual" and type in the name and port of my proxy, my password and my username the "Contacting Software Sites" process stays at 0%. Installing new software hangs at 10% of "Fetching children of <name of the software source> instead. With Eclipse Oxygen the network did work if the connection method was set to "manual".
What's the scenario (steps) where you encounter this?
Howto reproduce: - Place your computer in a network that uses a proxy that requires authentification - Start up Eclipse - In the config dialogue go to General/Network - Set the provider to "Native" and fill in all proxy details. It doesn't matter if you fill in the password as you will never be asked for it - press "OK" - Help/Check for updates - The status bar of Eclipse will be stuck at "Contacting Software Sites: (0%)
(In reply to Gunter Königsmann from comment #2) > Howto reproduce: > - Place your computer in a network that uses a proxy that requires > authentification > - Start up Eclipse > - In the config dialogue go to General/Network > - Set the provider to "Native" and fill in all proxy details. It doesn't > matter if you fill in the password as you will never be asked for it > - press "OK" > - Help/Check for updates > - The status bar of Eclipse will be stuck at "Contacting Software Sites: (0%) Do you also see this with other connections or only when installing or updating software?
Trying to connnect svn servers times out with Photon => The problem doesn't seem to be limited to updating.
Now old Eclipse versions, too, have stopped working from here => seems like something has changed in the network => Will close this ticket hoping we find the error from our side.
