Opened 16 years ago
Closed 14 years ago
#2870 closed defect (fixed)
No Update Behind Proxy
Reported by: | Rob | Owned by: | |
---|---|---|---|
Component: | host support | Version: | VirtualBox 3.0.8 |
Keywords: | Proxy | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
The VB GUI attempts to both register and update while behind the corporate proxy. IE and Firefox are both configured with the proxy. Either grab the information from them or allow the user to add this information within the settings somewhere.
Attachments (2)
Change History (19)
by , 16 years ago
Attachment: | VirtualBox-18022009_144825.jpg added |
---|
comment:1 by , 16 years ago
I have the same problem with v2.1.4. I try with 2 different proxy Microsoft Proxy Server and Freeproxy, and it's the same. Do you have find more information?
comment:2 by , 16 years ago
Hello, This problem already exists in V3.0. Also the menu entry Hilfe->Webseite (German maybe help->webpage in english) does not work.
comment:4 by , 15 years ago
Version: | VirtualBox 2.0.6 → VirtualBox 3.0.8 |
---|
comment:7 by , 15 years ago
The problem still persists in 3.1.0.
Is anybody looking at this ticket at all?
comment:9 by , 15 years ago
We'll look at it eventually, but there are many more important issues. Dismiss the dialog three times and it will not bother you again.
comment:10 by , 15 years ago
Same problem here but with a strange twist to it. I actually managed to download the guest additions three days ago. Now neither guest additions nor updates can be downloaded because the connection times out.
comment:11 by , 15 years ago
I'm seeing strange stuff here too, on OSX v3.1.2: using NAT to connect to my network (behind proxy) via wireless, a VH with Win Vista can get Win Updates, and IE can connect using "auto detect settings", but other applications (such as AVG Free 9 installer) fail to connect (even though AVG's install provides a dialog for proxy settings when a direct connect fails, the connection still fails after entering proxy info).
follow-up: 13 comment:12 by , 15 years ago
There is a demand of this options as well (v3.2.0). Especially when playing with test builds. Please, include also the option "Update only to stable builds". Proxy settings can be easily grabbed from IE (maybe there is a standard way to go via IE proxy in Windows?).
comment:13 by , 14 years ago
We just had to implement a proxy server for PCI-DSS and same here--no update checking because it can't see the proxy server. Windows 64-bit.
comment:14 by , 14 years ago
VirtualBox 4.0.8 here and corporate firewall policy mandates use of HTTP proxy. VB cannot update in this environment.
comment:15 by , 14 years ago
To all the whiners around here: Grab the newest 4.1.0_BETA and test Proxy.
http://forums.virtualbox.org/viewforum.php?f=15
-Technologov
comment:16 by , 14 years ago
I didn't realize that reporting bugs and describing issues on a bug tracker constituted as "whining", especially as this has been a long-standing issue through multiple releases. But anyway: thanks for the tip!
comment:17 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Should be finally implemented in 4.1.0.
Registration Error MessageBox