2

Some days ago, VirtualBox started to fail when I'm connected to a VPN. If my computer isn't connected to the VPN, everything works fine. I can start VMs, stop them, and so on. But if my computer is connected to the VPN, I get these messages:

$ VBoxManage controlvm myvm pause
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

This is my configuration:

  • Mac OS X El Capitan
  • VirtualBox 5.0.26 r108824
  • Tunnelblick 3.6.7c (build 4606) as VPN client
  • OpenVPN server 2.1.3

Just in case, the OpenVPN server is not installed on my computer. It's on a server in my new office.

What would be the problem?

EDIT: I just connected to a different VPN and VirtualBox worked with no problem. Now I'm sure the problem is caused for some configuration in the OpenVPN server.

Improve this question
4
  • 1
    A wild guess would be that VBoxManage uses some kind of IP socket to some other process which actually manages the VMs. When connected to the VPN, your network configuration is changed in a way that confuses VBoxManage about how to connected to the daemon.
    – Zoredache
    Commented Oct 6, 2016 at 18:59
  • Did you resolve the problem?
    – Vadim Shender
    Commented Jan 16, 2017 at 8:36
  • 1
    @VadimShender Yes! Some months ago. I just added as an answer.
    – JonDoe297
    Commented Jan 16, 2017 at 16:25
  • @JonDoe297, thank you for the answer!
    – Vadim Shender
    Commented Jan 17, 2017 at 11:05

1 Answer 1

Reset to default
2

In my OpenVPNAS server, I deleted the value on "Configuration > VPN Settings > Default Domain Suffix (optional)" and VirtualBox worked again.:

OpenVPNAS Screenshot

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .