Checking for new VirtualBox version error

[CyberManifest]

I have installed VirtualBox 5.0.0 r101573 on a MacBook Pro (Retina, 13-inch, Early 2015) running Mac OS X 10.10.4 Yosemite 64 bit host, and VirtualBox cannot connect to check for updates. The error I instantly receive is as follows:

The network operation failed with the following error: Unknown reason.

Please see the image...
http://cl.ly/image/3Y2b3h360K42/Screen% ... 9%20PM.png

I've updated the Ticket #13096 (https://www.virtualbox.org/ticket/13096) in hopes this will get resolved.
Also of note I encountered this same problem with the latest test build of VirtualBox but did not previously have problems before 5.0.0.

[Ferry]

Hello,

I experience the same error while checking for updates. Fresh install on OSX 10.10.4 Yosemite with both the (Stable) VirtualBox-5.0.0-101573-OSX and VirtualBox-5.0.1-101955-OSX (latest test build) version.

Next to that keeps my OVF imported guest rebooting with the error message:

"System is starting...."
Abort booting! app 1
unknown operation mode (0)

Help on the rebooting is more than welcome as I can't find a thing about it.

Grz,
Ferry

[loukingjr]

Help on the rebooting is more than welcome as I can't find a thing about it.

Grz,
Ferry

You should open a new post if you have a different problem. An OVF problem has nothing to do with checking for updates.

FWIW, Checking for updates works fine for me.

[CyberManifest]

Help on the rebooting is more than welcome as I can't find a thing about it.

Grz,
Ferry

You should open a new post if you have a different problem. An OVF problem has nothing to do with checking for updates.

FWIW, Checking for updates works fine for me.

You mention it works for you but fail to say on what host system or what version of VirtualBox you are using. That information may be helpful in narrowing down the problems others are experiencing.

[loukingjr]

True. OSX 10.10.3, 10.10.4 & 10.11 Beta (15A244d). VB 5.0.0 - 5.0.1-r101955.

[CyberManifest]

True. OSX 10.10.3, 10.10.4 & 10.11 Beta (15A244d). VB 5.0.0 - 5.0.1-r101955.

Odd, are you using all 64 bit (Hosts and Guests)?
I'm still getting the error even after upgrading to OS X 10.10.5 still using VB 5.0.0 64 bit and only have Windows 10 Pro 64 bit guest VM

[loukingjr]

There are no 32bit versions of OSX anymore. But 99% of the guests are 64bit but that would have nothing to do with Checking for updates either.

Try disabling the Mac's Firewall and see if that helps. Or any Anti-Virus program you run that has a Web Shield.

[michaln]

Yes, the update check is broken -- but it's only apparent on some systems.

VeriSign moved things around, but many systems have the information already cached in vbox-ssl-cacertificate.crt (a file in the VirtualBox settings directory). If a system already has the file, update checks will work. If not, they won't, and it's not correctly diagnosed ("unknown reason").

[loukingjr]

Interesting. I have 3 different Macs running versions of OSX/VirtualBox and Checking For Updates works on all of mine. Just lucky it seems.

[CyberManifest]

There are no 32bit versions of OSX anymore. But 99% of the guests are 64bit but that would have nothing to do with Checking for updates either.

Try disabling the Mac's Firewall and see if that helps. Or any Anti-Virus program you run that has a Web Shield.

I don't have a Firewall on and don't use any Anti-Virus programs. Still not able to check for updates.

[CyberManifest]

Yes, the update check is broken -- but it's only apparent on some systems.

VeriSign moved things around, but many systems have the information already cached in vbox-ssl-cacertificate.crt (a file in the VirtualBox settings directory). If a system already has the file, update checks will work. If not, they won't, and it's not correctly diagnosed ("unknown reason").

I just experienced the problem on a new install of VirtualBox 5.0.2 on a different system. Why is the vbox-ssl-cacertificate.crt not being created on install?